Tracify allows you to export your reporting and attribution data via Webhook. With this system you can configure a scheduled job with specific report settings to run at a regular cadence. In this way you can receive daily numbers across your campaigns and channels, configured to your preferred attribution settings.
Some webhook implementations focus on passing data for individual events. Tracify data doesn’t fit well within this model, instead our webhook service is similar to a scheduled reporting service, where all campaign data within your configuration will be delivered to your system according to your schedule.
A few examples of data you can export
To setup a webhook you’ll need to configure a few fields
| Date Range | Select the range of data you would like exported. Choosing yesterday will return one day’s data. Choosing last 7 days will send the last 7 days worth of data.
⚠️ A note about including “Today” as your date range
If you decide to include “Today” in your date range please note that this data is more limited, and does not include metrics such as ad spend or ROAS.
Please see below for more information about data structure and availability. | | --- | --- | | Attribution Window | Select the length of your conversion attribution window. This is the time period you want to consider conversions valid as an attribution signal for your campaigns. | | Attribution Model | Select your preferred attribution model e.g. Last Click, U-Shaped, etc. | | Attributed By | Select whether you want your conversions to be modeled by the click date or conversion date. | | Schedule | Choose your schedule cadence for data delivery. This is how often your webhook will run. For example, choose daily if you want to receive data every day.
Note, that depending on the date range you choose, you may get the same data twice. This could be useful, but in most cases it is more efficient to match your date range for data to your schedule. | | Touchpoints | Select the touch points you would like considered in your attribution.
Excluding a touchpoint will assign the weight of conversions to that touchpoint to other touch points in the journey (if available) | | Callback URL | Enter the URL of your server where you would like to receive your data. This URL needs to be configured to receive a JSON payload. | | Daily Breakdown | If selected, your returned data will be split by day. | | New vs. Returning | If selected, your returned data will be split by new and returning visitor. | | Discounts & Cooperations | If selected, your influencer campaign data will be split by discount code and cooperation id. |
The following are examples of how your data will be formatted in JSON
{
"created": "2023-07-13 19:37:03",
"format": "flatty",
"results": [
{
"dimensions": {
"accountID": "123456",
"adID": "123",
"adName": "MyAd",
"adsetID": "234",
"adsetName": "MyAdset",
"campaignID": "345",
"campaignName": "MyCampaign",
"cooperationLinkID": "",
"discountCode": "",
"source": "tiktok",
"storeID": "12341234-1234-1234-1234-123abc123412",
},
"infos": {
"adDeliveryStatus": "ENABLE",
"adsetDeliveryStatus": "ENABLE",
"buyingType": "",
"campaignDeliveryStatus": "ENABLE"
},
"metrics": {
"aov": 52.8,
"cac": 39.2,
"clicks": 76,
"cpc": 0.5157894736842106,
"cpm": 2.47,
"cpo": 39.2,
"cr": 0.019230769230769232,
"ctr": 0,
"frequency": 1.1662503673229503,
"impressions": 15875,
"landingPageViews": 0,
"linkClicks": 0,
"orderedItems": 1.0,
"orders": 1,
"reach": 13612,
"revenue": 52.8,
"roas": 1.3469387755102038,
"spend": 39.2,
"uatc": 10,
"ucv": 52,
"upv": 52
}
}
],
"version": "v1"
}