At a glance: Identify your collaboration scenario, making sure you know what data to provide, who is responsible for it, and in what format to submit it.
Overview
DCP supports a variety of on-site and off-site use cases. Each use case requires a different setup, specifying which collaborator is responsible for preparing each data source and the format in which the data should be configured.
This article aims to help Commerce Media Networks (CMNs) and advertisers (brands) identify which use case applies to them. Once the appropriate use case is determined, the collaboration owner can assign the necessary preparation and configuration tasks to the relevant collaborators (For more information about task assignment, see: Assign configuration task.)
This is where the use case decision tree comes into play. It serves as a structured guide to help CMNs and advertisers define their use case and receive the corresponding preparation instructions.
How the use case decision tree helps campaigns
The decision tree will help collaborators to:
- Identify who is responsible for preparing the conversion, ad engagement, or campaign mapping data—the CMN or the advertiser. Depending on the setup, one collaborator may need to prepare conversions and campaign mapping, and the other collaborator may need to prepare engagements.
- Find the preparation instructions matching your use case.
Collaborators need to specify:
- Whether they are using AppsFlyer SDK, server-to-server, or a custom data source for engagement and conversion data.
- Specify on whose platform - the CMN or the advertiser - the conversion events occur.
- Specify whether the platforms are app or web-based.
Now, let's explore the use case decision tree to determine the best data preparation strategy for your collaboration measurement.
Which decision tree do I need: Onsite or Offsite?
There are two decision trees you can use: one for on-site use cases and the other for off-site use cases. To determine which decision tree is appropriate, consider where the ad is served and where the conversion occurs.
- Use the off-site decision tree if the ad is displayed on an external advertising platform (e.g., Facebook, Google) outside of your owned and operated properties.
- Use the on-site decision tree if the ad is served within your ecosystem and the conversion takes place on your platform.
The on-site use case decision tree
In the on-site measurement scenario, the conversion takes place on a platform owned and operated by the CMN or the advertiser. This leads to the initial question in the on-site decision tree: On which platform does the conversion take place — the CMN’s or the advertiser’s?
Answer the initial question by choosing the correct answer, and continue to expand the branches that correspond to your specific conditions.
On which platform does the conversion take place?
The conversions take place on the CMN platform
The CMN platform is an app
If the CMN platform is an app, follow the instructions below for each data type:
Conversions
- The conversion data should be prepared and configured by the CMN.
- The conversion data is provided to DCP by either:
- in-app events (requires the AppsFlyer SDK integrated into your app). See the preparation instructions for conversion in-app events.
- or custom source. See the preparation instructions for the conversion custom source.
Engagements
- The engagement data should be prepared and configured by the CMN.
- The engagement data is provided to DCP by either:
- in-app events (requires the AppsFlyer SDK integrated into your app). See the preparation instructions for engagement in-app events.
- or custom source. See the preparation instructions for the engagement custom source.
Mapping
- Your campaign mapping source should be prepared and configured by the CMN.
- The campaign mapping data is provided to DCP by a custom data source. See the preparation instructions for the campaign mapping custom source.
OR
The CMN platform is a website
If the CMN platform is a website, follow the instructions below for each data type:
Conversions
- The conversion data should be prepared and configured by the advertiser.
- The conversion data is provided to DCP by a custom data source. See the preparation instructions for the conversion custom source.
Engagements
- The engagement data should be prepared and configured by the CMN.
- The engagement data is provided to DCP by a custom data source. See the preparation instructions for the engagement custom source.
Mapping
- Your campaign mapping source should be prepared and configured by the CMN.
- The campaign mapping data is provided to DCP by a custom source. See the preparation instructions for the campaign mapping custom source.
OR
The conversions take place on the advertiser platform
The advertiser platform is an app
If the advertiser platform is an app, follow the instructions below for each data type:
Conversions
- The conversion data should be prepared and configured by the advertiser.
- The conversion data is provided to DCP by either:
- in-app events (requires the AppsFlyer SDK integrated into the advertiser app). See the preparation instructions for conversion in-app events.
- or custom source. See the preparation instructions for the conversion custom source.
Engagements
- The engagement data should be prepared and configured by the CMN.
- The engagement data is provided to DCP by either:
- in-app events (requires the AppsFlyer SDK integrated into the CMN app). See the preparation instructions for engagement in-app events.
- or custom source. See the preparation instructions for the engagement custom source.
Mapping
- Your campaign mapping source should be prepared and configured by the advertiser.
- The campaign mapping data is provided to DCP by a custom data source. See the preparation instructions for the campaign mapping custom source.
OR
The advertiser platform is a website
If the advertiser platform is a website, follow the instructions below for each data type:
Conversion
- The conversion data should be prepared and configured by the advertiser.
- The conversion data is provided to DCP by a custom data source. See the preparation instructions for the conversion custom source.
Engagement
- The engagement data should be prepared and configured by the CMN.
- The engagement data is provided to DCP by a custom data source. See the preparation instructions for the engagement custom source.
Mapping
- The campaign mapping source should be prepared and configured by the advertiser.
- The campaign mapping data is provided to DCP by a custom data source. See the preparation instructions for the campaign mapping custom source.
The off-site use case decision tree
In the off-site measurement use case, the ad is displayed on an external advertising platform such as Facebook or Google. This leads to the initial question in the off-site decision tree: Which account on the external advertising platform is used to display the ad—the CMN’s or the advertiser’s?
Answer the initial question by choosing the correct answer, and continue to expand the branches that correspond to your specific conditions.
Which account on the external platform displays the ad?
The CMN external platform account
The conversions take place on the CMN platform
The CMN platform is an app
If the CMN platform is an app, follow the instructions below for each data type:
Conversions
- The conversion data should be prepared and configured by the CMN.
- The conversion data is provided to DCP by in-app events (requires the AppsFlyer SDK integrated into your app). See the preparation instructions for conversion in-app events.
Mapping
- Your campaign mapping source should be prepared and configured by the CMN.
- The campaign mapping data is provided to DCP by a custom data source. See the preparation instructions for the campaign mapping custom source.
OR
The CMN platform is a website
Not supported yet
OR
The conversions take place on the advertiser platform
The advertiser platform is an app
If the advertiser platform is an app, follow the instructions below for each data type:
Conversions
- The conversion data should be prepared and configured by the CMN.
- The conversion data is provided to DCP by in-app events (requires the AppsFlyer SDK integrated into your app). See the preparation instructions for conversion in-app events.
Mapping
- Your campaign mapping source should be prepared and configured by the CMN.
- The campaign mapping data is provided to DCP by a custom data source. See the preparation instructions for the campaign mapping custom source.
OR
The advertiser platform is a website
Not supported yet
OR
The Advertiser's external platform account
The conversions take place on the CMN platform
The CMN platform is an app
If the CMN platform is an app, follow the instructions below for each data type:
Conversions
- The conversion data should be prepared and configured by the CMN.
- The conversion data is provided to DCP by in-app events (requires the AppsFlyer SDK integrated into your app). See the preparation instructions for conversion in-app events.
Mapping
- Your campaign mapping source should be prepared and configured by the CMN.
- The campaign mapping data is provided to DCP by a custom data source. See the preparation instructions for the campaign mapping custom source.
OR
The CMN platform is a website
Not supported yet
OR
The conversions take place on the advertiser platform
The advertiser platform is an app
If the advertiser platform is an app, follow the instructions below for each data type:
Conversions
- The conversion data should be prepared and configured by the advertiser.
- The conversion data is provided to DCP by in-app events (requires the AppsFlyer SDK integrated into your app). See the preparation instructions for conversion in-app events.
Mapping
- Your campaign mapping source should be prepared and configured by the advertiser.
- The campaign mapping data is provided to DCP by a custom data source. See the preparation instructions for the campaign mapping custom source.
OR
The advertiser platform is a website
Not supported yet