The StackAdapt Conversions API Program for Offline Conversions
The StackAdapt Conversions API Program for Offline Conversions enables advertisers to send offline conversion data to StackAdapt. StackAdapt performs attribution analysis on the impact of the advertiser’s StackAdapt campaign on offline conversions. This allows customers to understand how StackAdapt campaigns drive offline conversions and to find additional data to better optimize ad spend or customer experience.
Use this program to understand Sales Attribution and Lift Insights on the StackAdapt platform.
Note
StackAdapt must approve all program participants. Contact your LiveRamp or StackAdapt representative to find out about getting approved for the StackAdapt Conversions API Program.
The StackAdapt Conversions API Program for Offline Conversions was formerly known as "the StackAdapt Attribution Program".
Overview of Steps Involved
The following steps need to be performed for each campaign to enable the attribution analysis in StackAdapt:
You send LiveRamp a sample conversion data file.
You activate your campaigns on StackAdapt.
LiveRamp creates an additional LiveRamp Connect account for the purpose of uploading your conversion data.
You upload conversion data from the last 90 days to LiveRamp.
LiveRamp matches your PII to RampIDs and sends it to StackAdapt along with your transaction data.
You work with your StackAdapt representative to complete the process in order to access your attribution reports.
See the appropriate sections below for more information on performing these steps.
Format the Conversion Data File
Tip
To download an Excel file template that contains all possible columns and formatting instructions, click here.
After transferring your data into the file template, be sure to delete the row with the formatting instructions and save the file in one of our allowed file types (.csv, .tsv, .psv, or .txt) before uploading.
Once the file has been formatted correctly, upload the file to LiveRamp. See the “Upload the File” section below for more information.
Note
Once you set up the file format for an existing conversions program feed, try to keep the file format (such as the column headers or the column order) the same for all subsequent files. If you change the file format for an existing feed, create a support case before uploading the new file to ensure your existing feeds are not impacted. For more information, see "Changing the Format of an Existing File".
List of All File Columns
See the table below for a list of columns and formatting instructions:
Field Name | Column Required? | Values Required? | Notes |
---|---|---|---|
first_name | Yes | Yes (if name and postal address (NAP) is used as an identifier) | |
last_name | Yes | Yes (if NAP is used as an identifier) | |
address_1 | Yes | Yes (if NAP is used as an identifier) | |
address_2 | Yes | No |
|
city | Yes | Yes (if NAP is used as an identifier) | |
state | Yes | Yes (if NAP is used as an identifier) |
|
zip | Yes | Yes (if NAP is used as an identifier) |
|
email_1 | Yes | Yes (if email address is used as an identifier) |
|
email_2 | Yes | No |
|
email_3 | Yes | No |
|
email_4 | Yes | No |
|
transaction_category | Yes | Yes |
|
transaction_timestamp | Yes | Yes |
|
transaction_amount | Yes | Yes |
|
phone_1 | Yes | Yes (if phone number is used as an identifier) |
|
phone_2 | Yes | No |
|
order_id | Yes | Yes |
|
store_id | No | No |
|
quantity | No | No |
|
brand | No | No |
|
region | No | No |
|
department | No | No |
|
product_id | No | No |
|
product_name | No | No |
|
product_category | No | No |
|
product_subcategory | No | No |
|
product_brand | No | No |
|
product_price | No | No |
|
promo_code | No | No |
|
GTIN | No | No |
|
custom_# | No | No |
|
Header Row Example
first_name|last_name|address_1|address_2|city|state|zip|email_1|email_2|email_3|email_4|transaction_category|transaction_timestamp|transaction_amount|phone_1|phone_2|
Conversion Data Examples
Alex|Chen|44 Main Street|#12|San Francisco|CA|94101|4371|alex@gmail.com|ac@ymail.com|||New Customer|2017- 02-07T13:25:00Z|99.99|5551234567|4152234123|USA|California|In-store|Bayfair Mall
Julian|Rogers|55 Mission Street||San Francisco|CA|94500|8435|julian@gmail.com||||Active Customer|2017- 03-07T15:15:00Z|127.18|5559994567
Send Conversion Data to LiveRamp
To set up the integration, send us a sample conversion data file. This file should contain at least 25 rows and each row should have values for the required fields (you can use placeholder data). Include all the possible transaction category values you plan on using in the “transaction_category” field and include only those values in subsequent files.
Once your campaign has started, send conversion data to LiveRamp at your preferred cadence. Files can be delivered at any cadence (daily, weekly, monthly, etc.), but do not send more than one file per day. LiveRamp’s preference is daily or weekly as this is a common requirement for other conversions programs.
Tip
Most customers automate this process to send files on a regular cadence.
Caution
Most platforms require that at least 1,000 unique transaction events be uploaded over a 28-day period.
Conversion Data Guidelines
Each conversion data record must include at least one PII identifier (name and postal address, email, or phone) and the required conversion data:
Transaction category
Transaction timestamp
Transaction amount
Order ID
Other optional conversion data (such as product data or quantity) can be included as well. See the “Format the Conversion Data File” section above for more information.
Make sure to also follow these additional guidelines:
Avoid sending duplicate transactions (transactions already sent to LiveRamp). If you send weekly or monthly files, only send transactions that occurred since the previous file was sent.
Do not include transactions that exceed the lookback window. All transactions sent to LiveRamp must have been created in the last 90 days.
Do not include conversions with a conversion date in the future.
Do not include conversion data that has already been sent in a previous file.
Upload the File
Upload conversion data files using LiveRamp’s SFTP server or your SFTP server.
You can also have us pull files from an AWS S3 bucket or GCS bucket. See “Getting Your Data Into LiveRamp” for more information.
Caution
Files for the this program cannot be uploaded via Connect. We recommend either uploading via our SFTP server, or having us pull files from an S3 bucket or GCS bucket.
To upload files using LiveRamp's SFTP: Use the credentials provided by your technical contact once the agreement has been signed and follow the instructions in “Upload a File via LiveRamp's SFTP”.
To upload files using your SFTP: Follow the instructions in “Upload a File via Your SFTP”.
After uploading, contact your Customer Implementation specialist to confirm that you have uploaded conversion data. The Customer Implementation specialist will ensure that the file is processed, and will instruct you where to upload future files.
Note
For future uploads, you do not have to email LiveRamp to confirm that you have uploaded data assuming headers have not changed or additional columns have not been added.
Once the file is uploaded, information on file processing status can be viewed in Connect (see "Check File Processing Status" for more information).
Most customers automate this process to send files on a regular cadence. Confirm your upload cadence with your Customer Implementation specialist.
Check File Processing Status
You can check the status of the files you've uploaded on the Files page in Connect. See "Check the Status of an Uploaded File" for complete instructions.
Note
Once you've uploaded a file, it can take up to 20 minutes before the file appears associated with the appropriate audience(s) on the Files page. If the file does not appear after at least 20 minutes, create a support case.
Files for this program use our Measurement Enablement workflow, and so the column headings that display on the Files page will look different from the ones that display for files that use our Activation workflow.
FAQs
At what cadence should I send my conversion data files?
LiveRamp can receive conversion data files for this conversions program on a daily, weekly, or monthly basis, but we highly suggest automated daily delivery as it gives LiveRamp the greatest ability to match. If you prefer not to send daily files, the next best option is weekly delivery as this enables data to be reported within the same month.
What conversion data should I include in my conversion data file?
Include all traceable offline transactions in your delivery. Do not include transactions with a transaction date in the future.
Avoid sending duplicate transactions (transactions already sent to LiveRamp). If you send daily files, only include transactions that occurred on that day. If you send weekly or monthly files, only send transactions that occurred since the previous file was sent.
Do not include transactions with a transaction date in the future.