The conversion in-app event must include the SKU information nested in the af_order_info key. 

"event_value": {
    "event_id": "<event_id>",
    "af_content": "retail",
    "af_order_id": "637f7c400f0e3fddd9e5bcbc",
    "af_order_info": [
        {
            "sku": "a",
            "revenue": 1.1,
            "qty": 2
        },
        {
            "sku": "b",
            "revenue": 100.5,
            "qty": 1
        }
    ]
}

For information about how to prepare in-app events, see the Create in-app events section below.

On-site campaigns can receive engagements via in-app events. The engagement in-app event should include the attribution data in the event_value key. See, as an example, the following event_value JSON structure:

"event_value": {
    "ad_name": "Spring_Sale_Ad_01",
    "ad_id": "ad_123456",
    "ad_type": "video",
    "adset_name": "Spring_Sale_Set_A",
    "adset_id": "adset_7890",
    "campaign_name": "Spring_2025_Promo",
    "campaign_id": "camp_456123",
    "channel": "facebook",
    "media_source": "meta_ads",
    "engagement_type": "click",
    "event_id": "evt_20250410_001"
}

You can use the fields below in your evant_value JSON key:

For more information, about how to prepare in-app events, see the Create in-app events section below.

To provide conversion and engagement data through in-app events configure the AppsFlyer SDK integrated into your app. For more information about creating in-app events, see:

• In-app events overview
• Implement in-app events in AppsFlyer SDK for developers

Use the scheme in the table below to create a conversion custom source file. 
The conversion scheme is unitary for off-site and on-site campaign types and for the different media partners.

Media partners: 

G: Google

M: Meta

Background colors: 

      Required fields

      Recommended fields

      Either of the selected fields is required

      Fields are hashed according to SRN-specified rules.

Use the schema below to create the engagement data source.

Use the schema below to create the campaign mapping source.

Before each attribution run, DCP loads campaign mapping records from the custom sources. You can choose between two modes for loading these records:

• Latest Strategy: DCP takes the most recent records based on the record upload date.

  For example, if the source contains records with upload dates of Jan 18, Jan 17, or Dec 29, the system will select the records with the Jan 18 date.

• Daily Strategy: DCP only takes records whose upload date matches the day of the attribution run. For example, if the run occurs at midnight on Jan 19, the system will only select campaign records with the Jan 19 upload date.

At the end of each day, DCP runs the attribution job for that day only if it can access the folder dedicated to that day and the conversion records within it. However, you can upload the folder for a certain day at a later date. For example, you can upload the Jan 17 folder on Jan 22.

• At the end of each day, DCP runs the attribution job for that day. The job will run only if DCP can find the folder for that day. The folder name is identical to the day name.
• The day folder can include records for events dating back 30 days from the day of the folder. For example, in the Jan 17 folder, the job processes records from December 18 to January 17.
• If you skip uploading the folder for a certain day, you have 30 days to upload it. For example, if you skipped uploading the Jan 17 folder, you can upload it until Feb 17. However, we recommend uploading it as close as possible to the folder date.
• If DCP does not find the current day’s folder, it will continue searching for the folder every 10 minutes for the next 7 days.

For each conversion record, DCP searches for the engagement events that triggered it.

• The engagement records are included in dated folders. However, you don’t have to upload an engagement folder for each day. For example, you can upload a Jan 13 and Jan 15 folder without uploading the Jan 14 folder. In this example, the records from Jan 14 will be taken from the Jan 15 folder.
• The attribution job for a given conversion folder will start only if an engagement folder with the same date as the conversion folder or a later date exists. For example, the attribution job for the Jan 17 conversion folder will start only if the Jan 17 engagement folder or folders with later dates, such as Jan 18, exist.
• The attribution job collects all engagement events that fall within the engagement lookback window.

Conversion and engagement data can come from in-app events, custom sources, or a combination of both. DCP lets you choose whether to use a single mode or mix them, allowing conversions to come from in-app events while engagements are sourced from custom files, or vice versa.

When configuring in-app events for conversions, engagements, or both, you must specify the app ID and the conversion or engagement event name. At the end of the day, the attribution job selects all events with the specified name and app ID that have the same event date as the conversion day.