Data Collaboration Platform (DCP) - Configure collaboration measurement

1. In AppsFlyer, from the side menu, go to Collaborate > Data Clean Room.
2. On the Data Collaboration Platform page, select the relevant collaboration.
3. At the bottom of the collaboration page, click Set up measurement (If the button is disabled, set up the data sources and audiences of the collaboration.)
4. On the Manage measurement page, choose  On-site or    Off-site as the activation type.
5. Continue to set up the collaboration measurement.

To assign any of the above tasks, follow the steps below:

1. Go to collaboration measurement, see Access collaboration measurement.
2. In each of the four tasks above, from the Assignee list, select the collaborator who will handle the task.

In some cases, it may be necessary to revoke a configuration task assignment from a collaborator. When the collaboration owner removes an assignment, the following occurs:

• The collaborator immediately loses access to the unassigned task.
• Any configuration previously provided by the collaborator for that task is discarded.
• The collaboration measurement is stopped.

To remove a configuration task assignment follow the steps below:

1. Go to collaboration measurement, see Access collaboration measurement.
2. In the relevant configuration step, from the Assignee list, remove the assigned collaborator.

After selecting on-site activation, continue setting up the campaign mapping data source.

Prerequisite: Before you set up the mapping source in DCP, create a campaign mapping custom source and upload it to your cloud service. For more information about the campaign mapping schema and instructions on creating a custom source and connecting it to a cloud service, see Prepare campaign mapping source.

To set up the campaign mapping source on DCP, perform the following:

1. Go to on-site collaboration measurement, see Access collaboration measurement.
2. Click Campaigns.
3. On the Campaigns dialog, click on + New campaign source:
4. In the New campaign source dialog that appears, enter the name of the campaign mapping source in the Source name field according to the following requirements and guidelines.
5. Click Next.
6. Under Set source location, select the connection from which the source is accessed.
   • If your account does not have connections defined, the New connection dialog will open, prompting you to create one.
   • If you have existing connections but want to use a new one, open the Select connection list and select + New connection.
7. Set the source access details according to the connected cloud service:
   • BigQuery
   • Snowflake
   • Amazon S3 and GCS
   • Local file system
8. Click Next.
9. Under Configure source structure, map the fields in your campaign mapping source to their corresponding DCP types. This mapping enables DCP to identify the source data fields.
   • For a list of the campaign mapping scheme fields and their descriptions, see The campaign mapping scheme.
   • For detailed information about how to perform the mapping, see Configure source structure.

10. Click Save. The campaign_mapping source created message is displayed.

    

11. In the Campaign dialog that appears, under Align collaborator names, map the collaborators' names as they appear in your campaign mapping source to the names found in AppsFlyer SalesforceDB.

    The alignment is necessary because there might be multiple collaborators in the campaign mapping source. In such cases, DCP must identify collaborators by their AppsFlyer SalesforceDB designation to correctly assign their campaign results.

    To align the collaborator name follow this step:

    • For each SalesforceDB collaborator name that appears in the ValueFound read-only field, assign a corresponding name from the list of collaborators’ names in the campaign mapping source.

After setting up the campaign mapping source, continue by setting up the conversion source.

Prerequisite: Before you set up the conversion source in DCP, you must create a conversion source file and upload it to your cloud service. For more information about the conversion source schema and instructions on creating a custom source and connecting it to a cloud service, see Prepare custom source files for engagements and conversions.

Alternatively, you can integrate the AppsFlyer SDK into your app and let it send in-app conversion events to DCP. For more information about the in-app events structure and how to create them, see Prepare in-app events for conversions and engagements events section of this document.

To set up the conversion source in DCP, perform the following:

1. Go to on-site collaboration measurement, see Access collaboration measurement.
2. Click Conversions.
3. On the Conversions dialog, select the conversion source type: in-app events or custom file.
   • In-app events — The origin of the conversion event data is the AppsFlyer SDK integrated into your app. The SDK sends conversion events in real time from your app whenever the user performs a converting activity. For more information about the in-app events structure and how to create them, see Prepare in-app events for conversions and engagements.
   • Your source — The origin of the conversion events is a custom source file stored in your cloud. For more information about the conversion custom source, see Prepare custom source files for engagements and conversions.
4. Depending on your selection enter the following details to configure the conversion source.
   • In-app events:
     1. Select the app that sends the in-app events containing the conversion data.
     2. In the Select conversion event list, select which of the in-app events sent by the AppsFlyer SDK is the conversion event. Each SDK event translates to a row in the conversion source.
     3. In the Advertised item (SKU) field, choose the parameter that contains the array of the conversion event SKUs.
   • Your source:
     1. Click on + New conversion source.
     2. In the New conversion source dialog, enter the conversion source's name in the Source name field according to the requirements and guidelines.
     3. Click Next.
     4. Under Set source location, select the connection from which the source is accessed.
        • If your account does not have connections defined, the New connection dialog will open, prompting you to create one.
        • If you have existing connections but want to use a new one, open the Select connection list and select + New connection.
     5. Set the source access details according to your cloud service:
        • BigQuery
        • Snowflake
        • Amazon S3 and GCS
        • Local file system
     6. Click Next.
     7. Under Configure source structure, map the fields in your conversion data source to their corresponding DCP types. This mapping enables DCP to identify the source data fields.
        • For a list of the conversion fields and their description, see The conversion source scheme.
        • For detailed information about how to perform the mapping, see Configure source structure.

5. Click Save. The conversion source created message is displayed.

   

After setting up the conversion source, continue by setting up the engagement source.

Prerequisite: Before you set up the engagement source in DCP, you must create an engagement source file and upload it to your cloud service. For more information about the engagement schema and instructions on creating a custom source and connecting it to a cloud service, see Prepare custom source files for engagements and conversions.

Alternatively, you can integrate the AppsFlyer SDK into your app and send engagement events to DCP. For more information about the in-app events structure and how to create them, see Prepare in-app events for conversions and engagements.

To set up the engagement source on DCP, follow these :

1. Go to on-site collaboration measurement, see Access collaboration measurement.
2. Click Engagements.
3. On the Engagements dialog, select the engagement source type: in-app events or custom file.
   • In-app events - the origin of the engagement events data is the AppsFlyer SDK integrated into your app. The SDK sends in-app events that include engagement data within their event_value parameter. For more information about the in-app events structure and how to create them, see Prepare custom source files for engagements and conversions.
   • Your source - the origin of the engagement events is a custom source file stored in your cloud. For more information about the conversion custom source, see Prepare in-app events for conversions and engagements.
4. Depending on your selection enter the following details to configure the engagement source.
   • In-app events:
     1. Select the app that sends the in-app events containing the engagement data.
     2. In Select ad engagement event, select which of the events sent by the AppsFlyer SDK is the event that includes engagement data. Each such event sent by the SDK translates to a row in the engagement source.
   • Your source:
     1. On the Engagements dialog, click on + New engagement source.
     2. In the New engagement source dialog, enter the conversion source's name in the Source name field according to the requirements and guidelines.
     3. Click Next.
     4. Under Set source location, select the connection from which the source is accessed.
        • If your account does not have connections defined, the New connection dialog will open, prompting you to create one.
        • If you have existing connections but want to use a new one, open the Select connection list and select + New connection.
     5. Set the source access details according to your cloud service:
        • BigQuery
        • Snowflake
        • Amazon S3 and GCS
        • Local file system
     6. Click Next.
     7. Under Configure source structure, map the fields in your engagement data source to their corresponding DCP types. This mapping enables DCP to identify the source data fields.
        • For a list of the engagement fields and their description, see The engagement source scheme.
        • For detailed information about how to perform the mapping, see Configure source structure.

5. Click Save. The engagement source created message is displayed.

   

After setting up the engagement source, continue by setting up the lookback window.

The lookback window is the maximum period during which an engagement (click or impression) can be considered for attribution to a conversion event. It specifies how many days back DCP searches for relevant engagements to match a particular conversion.

To set the lookback window, follow these steps:

1. Go to on-site collaboration measurement, see Access collaboration measurement.
2. Click Lookback window.
3. In the Click-through or View-through lookback window sliders, drag the pointer to choose the window duration in days.
4. Click Save.

After the configuration process is successfully completed, you can permit your collaborator to access the attributed measurement results by turning on the share toggle displayed in the completion dialog.

After selecting off-site activation, continue setting up the campaign mapping data source.

Prerequisite: Before you set up the mapping source in DCP, create a campaign mapping custom source and upload it to your cloud service. For more information about the campaign mapping schema and instructions on creating a custom source and connecting it to a cloud service, see Prepare campaign mapping source.

To set up the campaign mapping source on DCP, perform the following:

1. Go to off-site collaboration measurement, see Access collaboration measurement.
2. Click Campaigns.
3. In the Campaigns dialog, click on + New campaign source:
4. In the New campaign source dialog that appears, enter the name of the campaign mapping source in the Source name field according to the following requirements and guidelines.
5. Click Next.
6. Under Set source location, select the connection from which the source is accessed.
   • If your account does not have connections defined, the New connection dialog will open, prompting you to create one.
   • If you have existing connections but want to use a new one, open the Select connection list and select + New connection.
7. Set the source access details according to the connected cloud service:
   • BigQuery
   • Snowflake
   • Amazon S3 and GCS
   • Local file system
8. Click Next.
9. Under Configure source structure, map the fields in your campaign mapping source to their corresponding DCP types. This mapping enables DCP to identify the source data fields.
   • For a list of the campaign mapping scheme fields and their description, see The campaign mapping scheme.
   • For detailed information about how to perform the mapping, see Configure source structure.

10. Click Save. The campaign_mapping source created message is displayed.

    

11. In the Campaign dialog that appears, under Align collaborator names, map the collaborators' names as they appear in your campaign mapping source to the names found in AppsFlyer SalesforceDB.

    The alignment is necessary because there might be multiple collaborators in the campaign mapping source. In such cases, DCP must identify collaborators by their AppsFlyer SalesforceDB designation to correctly assign their campaign results..

    To align the collaborator name follow this step:

    • For each SalesforceDB collaborator name that appears in the ValueFound read-only field, assign a corresponding name from the list of collaborators’ names in the campaign mapping source.

After setting up the campaign mapping source, continue by setting up the conversion source.

Prerequisite: Integrate the AppsFlyer SDK into your app and set up in-app conversion events. For more information about the in-app events structure and how to create them, see Prepare in-app events for conversions and engagements.

To set up the conversion source in DCP, perform the following:

1. Go to off-site collaboration measurement, see Access collaboration measurement.
2. Click Conversions.
3. In the Conversions dialog, select the app that sends the in-app events containing the conversion data.
4. In Select conversion event, select which of the in-app events sent by the AppsFlyer SDK is the conversion event. Each event sent by the SDK translates to a row in the conversion source.
5. In Advertised item (SKU), choose the parameter that contains the array of the conversion event SKUs.

6. Click Save. The conversion source created message is displayed. 

   

After setting up the engagement source, continue by setting up the lookback window.

The lookback window is the maximum period during which an engagement (click or impression) can be considered for attribution to a conversion event. It specifies how many days back DCP searches for relevant engagements to match a particular conversion.

To set the lookback window, follow these steps:

1. Click Lookback window.
2. In the Click-through or View-through lookback window sliders, drag the pointer to choose the window duration in days.
3. Click Save.

After the configuration process is completed successfully, you can permit your collaborator to access the attributed measurement results by turning on the Share toggle in the completion dialog.