Cost ETL—granular campaign cost in a bucket

At a glance: Cost ETL, part of AppsFlyer ROI360, provides advertisers with campaign cost data having the best granularity available per media source. Data, updated 4 times daily, is delivered to your AWS S3 or GCS bucket ready for loading into advertiser BI systems.

5896_CostETL_graphic__2_.png

Cost ETL principles

Campaign cost data is written:

  • To your bucket for viewing, transferring, and loading cost data into your systems.
  • To the bucket four times per day (data freshness: intraday).
  • For the current day and the previous 6 days (referred to as 7 days in this article), as well as days 14, 29, and 88. The retroactive data allows for updates and corrections in the cost data reporting.
  • For cost matched with attribution, click, or impression.
    Note:
    • Data for the last 7 days is pulled anew from the media sources. Data for days 14, 29, and 88 is re-processed.
    • Only cost data is updated retroactively; not attribution data.

Data is provided with guaranteed primary dimensions:

  • Geo: breakdown by country
  • Channel: media source channel, for example, in the case of Google—YouTube

You can customize other dimensions and the metrics included in the reports to your needs.

View sample file. Note: The sample provided is an Excel file; Cost ETL files are sent to your bucket as parquet files. 

Implementation

Report dimensions

  • Reports are for all apps included in Cost ETL, per day, per batch. 
  • Each time data is written to the bucket, meaning 4 times a day, all available data is written, including the history, updates, and corrections of the previous 6 days, and days 14, 29, and 88. Take this into consideration in your data loading process. 
  • Reports structures are detailed in the file fields table. The structures are: 
    • Summary report is less granular (detailed) to enable easier and faster consumption.
    • Dimension reports have a primary dimension that is guaranteed. This means that the dimension is available for all media sources contained in that report. In contrast, if a media source does not provide the primary dimension data, that data is not included in the specific dimension report. Secondary dimensions are included when available. They are not guaranteed.
    • The primary (guaranteed) dimensions available are:
      • Geo: Data grouped by country
      • Channel: Media source channel, for example, YouTube in the case of Google and Instagram in the case of Meta ads.
    • You should use the dimensions and metrics that best fit your business needs. This may differ depending on the media source.

Directory and filename structure

  • Data written to the bucket has the directory and file structure described. View sample fileNote: The sample provided is an Excel file; Cost ETL files are sent to your bucket as parquet files. 
  • When Cost ETL completes writing to a directory, a flag is set by creating a success file. This is always the most recent timestamp in the directory. 
  • Each time data is written, it includes data for the current day and the previous 6 days (referred to as 7 days in this article), as well as days 14, 29, and 88.
  • The number of folders/files is as follows:
    • Summary: 4 batch folders per day.
      • Each batch folder contains parquet files with 7 days of data.
    • Dimensions: Each guaranteed dimension contains 4 batch folders per day.
      • Each batch folder contains parquet files containing data with numbering starting from 1.

Example directory structure

cost_etl_structure_4.jpg

Directory structure

/<advertiser bucket name>/cost_etl/version/dt=<yyyy-mm-dd>/b=<n>/
<dimension>/<file name>

Directory structure

Variable

Content

advertiser_bucket_name

As defined in the Cost ETL configuration: af-xpend-cost-etl-<af-account-id>-[your bucket name suffix]

cost_etl Always cost_etl 
version Cost ETL version
date

Cost date

Format: yyyy-mm-dd

batch Number 1-4
dimension

Data dimension:

  • geo
  • channel
file Numbered starting from 00001

File name structure 

part-<number>

Example

For the first data pull of June 23, 2020, the directory and file name structure is as follows:

/bucket-name/cost_etl/v1/dt=2020-06-23/b=1/geo/part-00001

File fields

Fields/Dimensions

Field

Remarks

Always populated

Format

Included in summary file

date

Date cost incurred reported by the media source

Yes

String yyyy-mm-dd

app_id

App id in the AppsFlyer platform

Yes

String

media_source

Media source responsible for display the ad

Yes

String

os

Operating system of the device. Possible values:

  • android
  • windowsphone
  • ios

Yes

String

-

agency

Agency responsible for placing the ad

No

String

-

campaign

Component of the advertising hierarchy

No

String

-

campaign_id

Component of the advertising hierarchy

No

String

-

adset

Component of the advertising hierarchy

No

String

-

adset_id

Component of the advertising hierarchy

No

String

-

ad

Component of the advertising hierarchy

No

String

-

ad_id

Component of the advertising hierarchy

No

String

ad_account

  • Ad account from which cost data was pulled
  • Relevant for networks where connection is done using oAuth (logging in with your credentials), for example in Google or Meta ads

No

String

-

currency

Currency of advertiser spend as defined for the app in AppsFlyer

Yes

3 character string compliant with ISO-4217

original_currency

Currency of cost as reported by the network before any conversions

Yes

3 character string compliant with ISO-4217

-

timezone

  • Timezone of the data as it is stored in AppsFlyer
  • Sometimes networks report data in a different time zone compared to what is defined in AppsFlyer. This data point helps explain cost discrepancies between AppsFlyer and networks

Yes

String 

-

geo

Dimension in the advertising hierarchy

No

2 character string compliant with ISO 3166

channel

Dimension in the advertising hierarchy

No

String

- 

keyword_term

Word(s) used by the user for online search

Yes

String 

-

keyword_id

ID of the ASA keyword terms

Yes

String

-

site_id

Publisher ID

No

String 

-

campaign_objective

Component of campaign properties. Learn more

No

String 

-

cost_model

Component of campaign properties. Learn more

No

String 

-

af_cost_model

Cost model mapped and normalized by AppsFlyer. Component of campaign properties. Learn more

No

String 

-

bid_strategy

Component of campaign properties. Learn more

No

String 

-

af_bid_strategy

Bid strategy mapped and normalized by AppsFlyer. Component of campaign properties. Learn more

No

String 

-

bid_amount

Component of campaign properties. Learn more

No

Integer

-

original_bid_amount

Component of campaign properties. Learn more

No

Integer

-

Metrics

Field

Remarks

Always populated

Format

Included in summary file

impressions

  • Counted by AppsFlyer.
  • Includes both UA and retargeting.

Yes.

If no value is available for a particular metric, it is populated with 0.

Integer

clicks

  • Counted by AppsFlyer.
  • Includes both UA and retargeting.

Integer

reported_impressions

Counted by the Media source

Integer

reported_clicks

Counted by the Media source

Integer

installs

Counted by AppsFlyer

Integer

reported_conversions

Counted by the Media source

Integer

 

re_engagements

Counted by AppsFlyer

Integer

re_attributions

Counted by AppsFlyer

Integer

cost

Amount of spend (including agency fees where relevant)

Value

original_cost

Cost as reported by the network, in the currency reported by the network before any currency conversion (with agency fees calculated by AppsFlyer added where relevant)

Value 

-

impressions_discrepancy

  • Difference between those counted by ad network and AppsFlyer
  • Disregard this metric if:
Integer

-

clicks_discrepancy

  • Difference between those counted by ad network and AppsFlyer
  • Disregard this metric if:
    • There isn't a match between cost and attribution.
    • The ad network doesn't support reported clicks.
Integer

-

installs_discrepancy

  • Difference between those counted by ad network and AppsFlyer
  • Disregard this metric if:
Integer

-

fees

Fees an agency charges in addition to the usual ad cost. Counted by AppsFlyer

Yes

Integer

-

cost_without_fees

Cost minus the agency fee. Counted by AppsFlyer

Yes

Integer

-

original_cost_without_fees

Original cost as reported by the ad network, without agency fees

Yes

Integer

-

ctr

  • Click-through rate. Counted by AppsFlyer
  • Formula: Click / impressions

 

 

 

 

No

Integer

-

cvr

  • Conversion rate. Counted by AppsFlyer
  • Formula: Install / clicks
Integer 

-

ecpm

  • Counted by AppsFlyer
  • Formula: (Cost / impressions) * 1000 
Integer

cpi

  • Counted by AppsFlyer
  • Formula: Cost / installs
Integer

ccvr

  • Cost per conversion
  • Formula: Cost / (installs + re-attributions + re-engagements)

Integer

cvvr

  • Completed video view rate. Counted by AppsFlyer
  • Formula: Video completions / impressions
Integer

-

reported_cvr

  • Reported conversion rate
  • Formula: Reported conversions / reported clicks
Integer

ecpc

  • Counted by AppsFlyer
  • Formula: Cost / clicks
Integer

-

video_25p_views

Video played 25%. Reported by  ad network

Integer

video_50p_views

Video played 50%. Reported by  ad network

Integer

video_75p_views

Video played 75%. Reported by  ad network

Integer

video_completions

Reported by  ad network

Integer

Set up Cost ETL for AWS S3

This configuration procedure must be performed by an admin user.

Before you start:

  • Setting up Cost ETL consists of setting up your AWS bucket (and giving AppsFlyer permission to write data in it), and setting up Cost ETL in AppsFlyer.
  • You will need both AWS admin privileges and access to the AppsFlyer UI to complete Cost ETL setup.
  • Keep tabs to both AWS and AppsFlyer open during setup. 
  • Note: KMS bucket encryption is not supported by AppsFlyer. 

AppsFlyerAdmin_us-en.png To set up your AWS bucket and Cost ETL:

  1. Sign in to the AWS console.
  2. Go to the S3 service.
  3. To create the bucket:
    1. Click Create bucket.
    2. Complete the Bucket name as follows: Start with the mandatory prefix af-xpend-cost-etl-acc-<af-account-id>- and then add a suffix as free text.
    3. Click Create bucket.
  4. In AppsFlyer, go to ROI360 > Cost ETL.
  5. Turn on Cost ETL.
  6. In Report schedule, select when you want to receive the first report. Subsequent reports arrive at approximately 6-hour intervals thereafter.
  7. Go to Amazon S3 settings.

  8. Select your S3 bucket region from the dropdown.
    If your region isn't displayed, contact your CSM. 
  9. Enter your Amazon S3 bucket name.
  10. Click Next.
    The bucket policy code snippet displays.

  11. Copy the bucket policy code snippet and paste it into your AWS settings.
    1. In AWS, Select the bucket you created for Cost ETL. 
    2. Go to the Permissions tab.
    3. In the Bucket policy section, click Edit.
    4. The Bucket policy window opens.
    5. Paste the bucket policy snippet into the window.
  12. In your AppsFlyer Cost ETL settings, click Next.
    The Validate bucket step displays. 
  13. Click Validate.
    Verify that Validation successful displays. 
  14. Click Next.
  15. Select one or more or all apps.  Select all to automatically include apps you add in the future.
  16. Click Apply
  17. Select at least one Guaranteed dimension: Channel and/or Geo.
  18. Select at least one additional dimension.

  19. Select at least one metric to be included in the reports. 

  20. Click Apply.

Set up Cost ETL for GCS

This configuration procedure must be performed by an admin user.

Before you start:

  • Setting up Cost ETL consists of setting up your GCS bucket (and giving AppsFlyer permission to write data in it), and setting up Cost ETL in AppsFlyer.
  • You will need both GCS admin privileges and access to the AppsFlyer UI to complete Cost ETL setup.
  • Keep tabs to both GCS and AppsFlyer open during setup. 

AppsFlyerAdmin_us-en.png To set up your GCS bucket and Cost ETL:

  1. Sign in to the GCS console.
  2. Create a bucket.
    Name the bucket as follows:
    • Start with the mandatory prefix af-xpend-cost-etl-acc-<af-account-id>- and then add a suffix as free text.
    • Your af-account-id can be found in the AppsFlyer UI as indicated in the following steps 6-8. 
    • See GCS bucket naming requirements.
  3. In AppsFlyer, go to ROI360 > Cost ETL.
  4. Turn on Cost ETL
  5. In Report schedule, select when you want to receive the first report. Subsequent reports arrive at approximately 6-hour intervals thereafter.
  6. Go to Data destination and select .
  7. Enter your GCS bucket name.
  8. Click Next.
    The AppsFlyer service account displays, to be used to set the GCS permissions.
  9. In your GCS console, set the IAM permissions for the bucket:
    1. Add the AppsFlyer service account as a principal to the Cost ETL bucket.

    2. Assign the role Storage Object Admin.
  10. In your AppsFlyer Cost ETL settings, click Next.
    The Validate bucket step displays. 
  11. Click Validate.
    Verify that Validation successful displays. 
  12. Click Next.
  13. Select one or more or all apps.  Select all to automatically include apps you add in the future.
  14. Click Apply
  15. Select at least one Guaranteed dimension: Channel and/or Geo.
  16. Select at least one additional dimension.

  17. Select at least one metric to be included in the reports. 

  18. Click Apply.

AWS object ownership

In AWS, by default, when AppsFlyer writes objects to your bucket, the object owner is AppsFlyer. Depending on your data loading process you might have to change the default ownership to you—the bucket owner.  

To change the ownership of objects in your bucket:

  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the Buckets list, choose the name of the bucket that you want to enable S3 Object Ownership for.

  3. Go to the Permissions tab.

  4. Under Object Ownership, click Edit

  5. Select Bucket owner preferred.

  6. Click Save.

Best practices

Override data

When pulling and analyzing your data, it is recommended to pull data for a specific date and batch, or override all previous data for the days that the current batch provides. Otherwise, you may see the same data repeated.

For example, batch 1 on February 20 contains data for Feb 14-20. But, batches written on February 19 also contained data for Feb 14 to Feb 19. Override the data of the previous days received on February 19 with the data received in the most recent February 20 batch.

Geo versus channel

Not all networks provide data for all dimensions together. Geo and channel data in Meta ads are the most common examples. This is why two separate data sets are provided. The geo data set is guaranteed to have geo data and the channel data set is guaranteed to have channel data.

In many cases and for many media sources, the data in the geo and channel sets will be identical. As such, consume one of the data sets (geo or channel), according to what best suits your needs.

If the integration agreement with a given media source doesn't include channel, so that channel is blank, we treat that data as if it contains the channel. 

Aggregate data

Cost ETL provides flexible and granular data as deep as can be extracted from the ad network. To extract actionable insight from such potentially huge amounts of data, it is recommended to aggregate the data in a way that best suits your business needs. For example, if you need to understand cost data at the campaign and country-level, use those dimensions.

Standardization across networks

Not all networks provide data with the same granularity. For example, Meta ads doesn't provide site ID cost data, while X Ads doesn;t provide geo cost data. Be aware of such cases as you aggregate Cost ETL data, and make sure you look at similar data as you compare networks.

Compare data

Cost ETL provides information regarding all your cost data. Some campaigns provided in Cost ETL do not appear in some AppsFlyer dashboards, for example, data of inactive campaigns, meaning campaigns without any recorded installs. To compare the data, find a specific campaign ID in the overview dashboard and compare it to its cost data in Cost ETL. Learn more about cost data availability

Traits and limitations

Trait Remarks
Timezone

If the time zone is changed, cost data is duplicated on the day of the change. Learn more

Data freshness

Intraday. Note: Once the cost data arrives to your bucket, further data transfer to your BI systems can vary greatly, depending on the report and parquet file size, which can be anywhere from a few KBs to many GBs.