Facebook and RedTrack

Intro

Both Facebook and Instagram have the same ad-managing interface (Facebook Ads Manager).

Our API Facebook integration enables you to:

Pass all conversion data, including extra conversions, back to Facebook and link it to campaigns for better optimization.
Automatically pause non-converting creatives and campaigns on Facebook, eliminating manual work.
Keep cost data updated in real time.

Redirect URLs are normally forbidden on Facebook.
There are limited cases when Facebook allows you to use the redirect link (e.g. RedTrack campaign tracking URL) but we as a service provider do not recommend it and cannot guarantee the safety of your tracking campaigns.

For all of your Facebook campaigns, no-redirect tracking with a custom tracking domain is better to be used.

Traffic filtering functionality is limited for Facebook and can be used for the Offer level only (for the cases when you run the traffic to the landing page first). For more details go to the Traffic filtering guide.

Due to Facebook restrictions, conversion data is delivered to your Facebook campaigns within 24 hours.

Parameters sent to Facebook upon conversion creation

The following parameters are sent to Facebook when a conversion is created in RedTrack:

Parameter	Description
FB click id	Facebook click ID, identifies the Facebook click that led to the conversion. Taken from sub 20 of the traffic channel.
Browser id	Facebook browser ID, used to identify a user’s browser for Facebook tracking. Taken from sub 19 of the traffic channel.
External id	External identifier for deduplication and attribution. Pulled from rtclickid.
Email	Hashed email address taken from the parameter assigned the Email role in the Offer Source.
Phone	Hashed phone number taken from the parameter assigned the Phone role in the Offer Source.
FirstName	Hashed first name taken from the parameter assigned the First Name role in the Offer Source.
LastName	Hashed last name taken from the parameter assigned the Last Name role in the Offer Source.
Birthday	Hashed birth date taken from the parameter assigned the Birthday role in the Offer Source.
Gender	Gender value taken from the parameter assigned the Gender role in the Offer Source.
Zip	Postal code value taken from the parameter assigned the Zip role in the Offer Source.
IP	IP address of the user at the time of the click, sourced from RedTrack click data.
UserAgent	Browser user agent string captured during the click.
City	Hashed city name derived from geolocation based on the click IP.
CityUnhashed	Plain text city name derived from IP geolocation during the click.
Country	Hashed country name based on IP geolocation at click time.
CountryUnhashed	Plain text country name from IP geolocation at click time.
State USA	Hashed U.S. state name based on click IP geolocation.
State USAUnhashed	Plain text USA state name based on click IP geolocation.
Currency	Currency for the transaction taken from click data.
Event ID	Unique event identifier used for event tracking. Can come from either rtclickid or an assigned role.
Event Name	Describes the type of conversion event (e.g., Purchase, Lead), based on conversion type.
Event Time	Timestamp of the conversion event in UTC, based on the conversion’s created_at time.
Event Source Url	URL of the page where the event occurred, defined in the offer form’s pixel settings.
ActionSource	Describes the source of the event action (e.g., website, app), set in the offer form’s pixel settings.
Revenue	Monetary value of the conversion taken from the conversion data.
Content Category	Hashed value indicating the category of the content or product, based on the assigned Content Category role in the Offer Source.
Content IDs	Product or content identifiers involved in the event, taken from the Content IDs role in the Offer Source.
Product Name	Name or title of the product/content involved in the conversion, taken from the Product Name role in the Offer Source.
Contents	Detailed list or array of products/content involved in the conversion, taken from the Contents role in the Offer Source.
OrderID	Unique order identifier for the transaction, sourced from either the order ID or rtclickid.
SubscriptionID	Identifier for a subscription or recurring event, based on rtclickid.

Integration

1. Add a custom tracking domain

1. Add a CNAME record pointing to your RedTrack default domain in your domain registrar.
2. On the left menu go to Tools → Domains → Create new domain.
3. The default domain is stated right on the top and looks like smth.rdtk.io.
4. Add the integrated domain to your RedTrack account and activate the Free SSL option.

Follow this guide for details on adding a custom tracking domain in RT.

2. Add the offer/website you are promoting

This is the target destination link where you plan to run the traffic: it can be an affiliate offer, a direct link to your website, or the shop.

How to add an offer (for Affiliates)

How to add a website/shop (for Advertisers)

1. Add the offer source: New from template/New from scratch → find the affiliate network you work with/add your custom name → Save.

Use the S2S postback URL available in the offer source settings to pass the conversion data back to RedTrack.

2. Add the offer link: Offers → New → choose the offer source from the list, add the offer URL → save the changes.

Add the click tracking parameter to the offer URL in RedTrack to pass the clickid to the affiliate network you work with.
For example: &affsub={clickid} where {clickid} is RedTrack parameter

More info on offer source and offer in RT can be found here.

1. Go to Brands → New → Add your brand (it is the name of your shop or your website).
2. On the same page, add the purchase data parameters – Name/Description is what you will see in reports – Roles define their use with CAPI.
3. Go to Websites → New → Add your website URL (this is your e-commerce shop/website link).
4. Follow the suggested steps to generate the scripts. You will need it later for your e-commerce platform.

More info on e-commerce platform integration is here.

3. Add Facebook traffic channel

1. Go to Traffic Channels → New from template → find Facebook → Add → Save:

You can modify some Facebook parameters in the opened template. Blocked (greyed) parameters should be used under the same sub-values with the same roles assigned as provided in the initial template.

The following parameters and their roles are essential for the API cost integration:
{{ad.id}} should always be with Aid role
{{adset.id}} should always be with Gid role
{{campaign.id}} should always be with Cid role

“fbclid” parameter is required for sending the conversion data back to Facebook. This parameter should always be the last in the line, meaning, that there should be no other parameters when you will add the parameters string to Facebook:

2. In the added template go to Facebook API Integration → Connect Facebook → verify your ad account:

Once you are redirected to your RedTrack account settings and see the Connected button, it means Facebook accepted the integration:

It is highly recommended to check the integration and reconnect your Facebook account with RedTrack every 2-3 months for the integration to be valid since Facebook can disconnect your account randomly for security reasons (you will notice that almost immediately since the cost data stops coming at that point).

4. Create a campaign in RedTrack

For Facebook, it is preferable to work either with a landing page before the offer, or direct linking to the offer/website if you have the page code edit rights since you will need to add the tracking script

If you are an affiliate

If you are an advertiser

For Facebook, it is preferable to work either with a landing page before the offer, or direct linking to the offer if you have the offer page code edit rights since you will need to add the tracking script

1. Create a campaign in RedTrack.

Campaigns → New → Fill in the info in all the sections and tabs:

General: Give it the name, and choose the traffic channel, tracking domain, and cost-tracking method.
Funnels: Choose the type of funnel you are using and add the elements from the drop-downs.
S2S postback: This field will be filled in automatically based on the data you have added to your traffic channel settings.
Auto update costs: Do not forget to turn the toggle on if you are working with the API-integrated traffic channel

Use this guide for more detailed info.

2. For Facebook tracking you will need to use the tracking script as we highly recommend working with no-redirect tracking. You will have to use our script on the page code, and choose the one that works best for you:

Simple script (one landing page, one traffic channel)
It is generated automatically once you save the campaign and is available under the no-redirect tab.

Advanced script (one landing page, multiple traffic channels)

For the cases when you plan to use the same lander with different traffic channels and need to separate the traffic,

2.1. Create a campaign for the organic traffic. With the same setup as for the paid traffic:

2.2. Tools → Scripts → New → Fill in the mandatory fields and save the changes

Script type – select one of the 3 types:
– default – choose this one if you plan to work with your website (e.g. e-com store) where a visitor can click on any link or visit any tab while the target action is tracked always on some other page no matter what the visitor path was before.
– /click support – use it when you lead the visitor from your landing page to a 3rd party offer and use domain.com/click CTA link format.
– /pre-click support – same as /click support but for a prelanding page with domain.com/preclick CTA link.

Title – give your script a name.
Domain – choose a custom tracking domain that will be used in that script.
Default campaign – organic traffic campaign created within step 2.1
Attribution – set the attribution model you want to use:
– First click – first recorded inbound click.
– Last click– last recorded inbound click.
– Last paid click – last recorded inbound click with tracking parameters.
Note: we always recommend using Last paid click attribution, since that in the most accurate way measures which marketing touchpoint a customer last clicked on or engaged with before purchasing, and gives it 100% of the credit.

Attribution window – set the attribution window, the period for the first click, and last paid click models.
Cookie domain – the root domain to place a cookie. This is the root domain of your website

2.3. Once you save the changes, the ready-to-use script will be generated, copy it

You will need to add the tracking parameters later on the Facebook side. The parameters depend on the type of script you have chosen before and can be taken from the “universal script” (advanced) or “no-redirect” (simple) tab within campaign settings:

It is preferable to place the tracking script at the end of the body section of the landing page.

1. Create a campaign in RedTrack.

Campaigns → New → Fill in the info in all the sections and tabs:

General: Give it the name, and choose the traffic channel, tracking domain, and cost-tracking method.
Funnels: Choose the type of funnel you are using and add the elements from the drop-downs.
S2S postback: This field will be filled in automatically based on the data you have added to your traffic channel settings.
Auto update costs: Do not forget to turn the toggle on if you are working with the API-integrated traffic channel

Use this guide for more info on campaign settings.

2. For Facebook you will need to use our universal tracking script.

The universal tracking script is created automatically once you’ve added the Website and can be taken from your RT account → Scripts. The script should be placed on the page code or for your e-commerce store/website (check out the precise e-commerce guide for details).

The tracking parameters are to be copied from the campaign settings and saved for later:

5. Verify the domain for Facebook

Due to the new Facebook policy, you should now verify the domain you will be using for your Facebook campaign. This is an action that should be done on your Facebook account.

Domains on Facebook can be verified in 3 ways:
– via meta tag
– via the uploaded HTML file
– via DNS record

For the domain verification procedure details on Facebook, check out the following guides:
– Domain verification in Meta Business Manager
– Methods of domain verification on Facebook

The steps below will demonstrate the DNS record management method.

1. Business Manager → Brand Safety and Suitability → Domains → Add → Create a new domain:

2. Paste your domain → Add:

Use the root domain without any prefixes:
Correct: website.com.
Incorrect: www.website.com or https://website.com.

Domains will not appear in your list immediately. Give the system some time to replicate the data.

3. Select the target domain → choose the DNS verification method:

4. Copy your unique TXT value:

5. Go to your domain registrar → open DNS settings and add a new record with the following values:

Host: @
Points to: your unique TXT record from point 4
TTL: the lowest possible

The steps you need to perform to add a DNS TXT record to your DNS settings may vary depending on the domain host. The screenshots in this article are examples from GoDaddy.

6. Give it some time for the data replication to happen (approximately 1 hour), then verify the domain in your Facebook domain settings:

Once the domain is verified, you’ll see a Verified tag next to the added domain:

7. Associate the domain with your page:

8. Get back to RedTrack → settings of the added Offer (for Affiliates)/ Website (for Advertisers) → CAPI (Maximize signals) → add the values for Default Action source and Default Event URL → Save changes to the template:

In the Default Action source select from the drop-down the type of the conversion to be set for Facebook API.
In the Default Event URL add the verified domain. The domain should be secure, use the following link format: https://your.domain.com.

If you don’t add the the values for Default Action source and Default Event URL in RedTrack, conversions will fail to attribute.

6. Generate the Conversion API Key

Your Facebook account → Events Manager→ pixel settings → Settings → Create Access Token:

Here is more about Conversion API Key in FB.

7. Find and copy your FB pixel

You can find your unique pixel ID in the Facebook campaign settings → Tracking:

8. Add the pixel to RedTrack

There are 2 ways of adding your FB pixel to RedTrack:

Via Offer/Website form, in which case all conversions associated with this offer will be sent to that pixel.
Via FB traffic channel, in which case only conversions attributed to this traffic channel will be sent to that pixel.

Adding pixel to both the offer form and FB traffic channel will lead to duplicates.

Decide on the way and act accordingly:

via FB traffic channel

via Offer/Website

If the pixel is added at the traffic channel level, only conversions attributed to this traffic channel will be sent.

Go to the settings of the added Facebook traffic channel → Facebook default data source (pixel) → add the the pixel, token and Default conversion name (if needed) → Save changes to the template:

Default Event name field hint:
– If the field remains empty, the default conversion is sent with the event under the name Purchase.
– If the field is filled in, the default conversion is sent with the name specified in that field.

Go to the settings of the added Offer/Website → CAPI (Maximize signals) → Add your Meta (FB) pixels to send the conversions with the Meta (FB) conversion API → add the the pixel, token and other needed values → Save changes to the template:

Aside from the mandatory fields like Pixel ID and Conversion API key for that pixel you can also set up the default values for the action source, event URL, and default event name to let the system use them for all your pixels:

Action source: we recommend using the Website option
Event URL: the domain verified for Facebook. Use the “https://domain.name” URL structure.
Default Event Name: this field is not available in the offer form but can be set in the Facebook traffic channel template. If you’ve already added the Pixel ID and API key in the offer form, you don’t need to enter them again in the traffic channel form. You only need to go there to set the Default Event Name.

Check out this video explanation of how RT Conversion API works for META (Facebook).

9. Set up the conversion events for Facebook

Setting up the events

– Conversion information will fall under your pixel/data source.
– We recommend keeping a Purchase name for one of your conversions so that you do not need to make any adjustments on the Facebook side since Facebook knows this name very well and will optimize the traffic better for a Purchase than a custom name (Sale, Conversion, etc.).

Conversion Matching (preferred method)

Adding non-standard conversion names (outdated way)

1. Add conversion events you want to track with RedTrack.

Tools → Conversion tracking → Conversion type → add the events you want to track → Save.

The fields are case-sensitive. The name should be exactly what you plan to send to RedTrack.
The system will automatically send your conversion types to Facebook exactly as you name them.

2. Now you can match the events in one of 2 ways:

– If you added your pixel to the Facebook traffic channel, you should match your events in the FB traffic channel template.
– If you added your pixel in the Offer form, you should match your events in the Offer form.

Custom event matching and default event matching cannot function simultaneously. You can EITHER enter a Default Event name OR enable Custom Conversion Matching and map events accordingly.

Facebook traffic channel template

Offer/Website form

Go to the added Facebook traffic channel template → Facebook default data source (pixel) → enable the Custom Conversion Matching toggle → match the events → Save changes to the template:

Events on your left are the ones you’ve added in RT in step 1. Events on your right are Facebook ones.

Go to the added Offer form → CAPI → enable the Custom Conversion Matching toggle → match the events → Save changes to the form:

Events on your left are the ones you’ve added in RT in step 1. Events on your right are Facebook ones.

Configuring conditional revenue for Facebook CAPI

RedTrack allows you to customize the revenue values sent to Facebook via the Conversions API (CAPI) based on the set Payout value. This feature enables more accurate revenue reporting and optimization in your Facebook Ads campaigns.

You can set up conditional revenue in either the Traffic Channel or the Offer/Website settings. Choose one, not both, to avoid duplicate conversions.

Configure the conditional revenue in the same place where you add your Facebook Pixel and API key. This ensures consistency across the pixel, event, and revenue data sent to Meta.

To set it up go to the template where you added your Pixel ID, API key, and matched the events → act accordingly:

Setup location is FB traffic channel template

Setup location is Offer/Website template

Facebook traffic channel → Facebook default data source (pixel) → navigate to the Payout type field next to Default Event name or/and Custom Conversion Type (depending on your setup) → choose the Payout type from the drop-down and assign the Value for it → Save changes:

Payout types explained:
– None: RedTrack will send the full revenue amount associated with the conversion event.
– Numeric: RedTrack will send this fixed amount as the revenue.
– Percentage: RedTrack will calculate and send the specified percentage of the revenue.

Example
Let’s break down the revenue configuration from the screenshot:

Once the Lead conversion type is triggered, regardless of the actual payout value associated with the conversion (e.g., whether it’s $100 or $10), RedTrack will send exactly 35 as the revenue value for this Lead event to Facebook via the Conversion API.

If the Payout type is configured for the same event in both the Default Event name and the Custom Conversion Matching section, the configuration set in Custom Conversion Matching section takes priority.

Offer/Website template → CAPI (Maximize Signals) → Add your Meta (FB) pixels to send the conversions with the Meta (FB) conversion API → navigate to the Payout type field next to Default Action source or/and Custom Conversion Type → choose the Payout type from the drop-down and assign the Value for it → Save changes:

Payout type configuration set up in the Custom Conversion Matching section takes priority over the one set up next to the Default Action source field.

1. Add conversion events you want to use.

Tools → Conversion tracking → Conversion type → add the events you want to track → Save.

The fields are case-sensitive. The name should be exactly what you plan to send to RedTrack.
The system will automatically send your conversion types to Facebook exactly as you name them.

If you are using non-standard names for the events you send to Facebook (something apart from Purchase, ViewContent, InitiateCheckout, Lead), you need to set them up on Facebook, too:

2. Events Manager → Custom conversions → Create custom conversion:

3. Fill in the fields in the pop-up window:

Name: give your custom conversion a name
(optional) Description: add a description to distinguish your custom conversion from others in the list
Data source: select the data source
Action source: select the action source to which your custom conversions are attributed (it should match with the one you will set inside RedTrack)
Event: select the event URL

If you select All URL traffic or a custom event, you’ll see the option to Choose a standard event for optimization. Facebook recommends you keep the category they chose for you. If you want to choose a different category, select the one that best describes the conversion event you’re optimizing.

Refer to this article to learn more about standard event categories on Facebook.

Rules: set the rules by URL or event parameters. You can select the parameters that you currently send with the event you selected. If you don’t see the parameter you want to choose, update your pixel or Conversions API setup to send the parameter with your event.

Parameters that follow the OR condition.
For example, if you create a custom conversion using a purchase event and type in Product A, Product B and Product C in the content_id parameter value, the custom conversion measures when someone purchases product A, B or C.

Rules that follow the AND condition.
For example, if you create 3 separate rules for content_id equals A, content_id equals B, and content_id equals C, the custom conversion measures when all 3 events occur.

Refer to this article for more info about Rules within this setup.

(optional) Enter a conversion value: click to check the box next to Enter a conversion value, then enter your value. Only use this field if the events in your custom conversion don’t have a conversion value.

Use only whole numbers, and don’t include any additional symbols.

Facebook guides on custom conversions that can also be useful:
▸ Filtering events in Meta Events Manager
▸ Best practices for custom conversion setup in Meta Events Manager
▸ How to edit custom conversions in Meta Events Manager
▸ How to delete custom conversions in Meta Events Manager

4. Once you’ve created your custom conversion, to activate it, navigate to the page of your website it’s referencing to trigger it. Then get back to the Events Manager → Custom conversions tab and see if the added conversion changed its status to Active:

10. (if you haven’t done it yet) Create an ad on Facebook

Ads Manager → Create Ad → create a new campaign or use an existing campaign → set up campaign parameters → copy paste your LP URL/Website URL (the link without tracking parameters) under the website URL → add additional tracking parameters (universal script or tracking parameters (UTMs)) in the “URL parameters” section

Make sure there are no special symbols and spaces (#, %, etc.) in the names of your ads, adsets, and campaigns – otherwise the data won’t be tracked.

– Facebook catches only the initial data for ads, adsets, and campaign names (even when some test name was added as a draft), it will ignore all name updates you make after.

– If you need to be sure you receive the correct names, add them to the tracking parameters manually or analyze the data by IDs instead:
cmpid=5f92a30bc860ee0001fa9996&sub1={{ad.id}}&sub2={{adset.id}}&sub3={{campaign.id}}&sub4=myad&sub5=myadset&sub6=mycampaign&sub7={{placement}}&sub8={{site_source_name}}

– If there are already some UTM parameters in the URL parameters field, you do not have to delete them, just append the parameters taken from your campaign in RedTrack to the already existing parameters with the help of the ampersand symbol: “&”.

Use this tutorial to help you add your LP URL and tracking parameters properly in Facebook Ads Manager.

11. (optional) Warm up your Facebook account with test conversions

This is an optional step. Warm up your account only if it is fresh and has no data / have a completely new empty account on Facebook.

Facebook will not accept your event until it considers this is a real event that can be used for optimization on its side.

To start running a live campaign, you need to make sure everything is up and running. And at this point, we will need to warm up your account with some fake conversions.

1. Once you’re done with the integration and have created a Facebook campaign, you need to run some live clicks from Facebook.

We will need them for conversion generation. To find your clicks, go to Logs → Clicks:

2. Tools → Conversion tracking → copy the link from the S2S conversion tracking field:

3. Put the clickid from step 1 instead of the replace_me part in the postback URL you copied within step 2.

Your link should look approximately like this: https://docs.trk.agency/postback?clickid=63e3788ca66ef500014a41ct

4. Paste the link to the browser and press enter. You should get this successful message:

5. The conversion will appear in your RedTrack account. Do the same with different click ids within a day. You will need approximately 20 conversions to warm up the account.

Don’t generate fake conversions simultaneously, as Facebook may not accept them.
Facebook needs a bit more time to attribute the conversions to your campaigns. It can take 48 to 72 hours to see the data.

12. Set up the automation

Set up the automation.

Use this guide to help set up rules.
Use this guide for setting up the auto-update cost feature.

Our tool also offers you the opportunity to manually switch on/off your Facebook Campaigns, Ad sets, or Ads without leaving RedTrack UI. Please check out a brief overview of the manual campaign management feature and contact [email protected] if you are interested.

13. Increase the event match quality

If you work with an affiliate offer, having a 10/10 match quality is impossible. There is a list of parameters Facebook wants to receive, but only half of them can be covered by any third-party tool. This causes the match quality to be at a low level. And it’s not something you should struggle with.

However, RedTrack has a feature that can help you to improve the event match quality with Facebook. It does not take any additional values from Facebook, but if you have them on your website/affiliate network side (for example, order ID at Shopify) or store them on your side, you can send them to RedTrack and then to Facebook to increase the event match quality.

Make sure the website (affiliate network) can send additional target parameters. You can clarify this question with your account manager if it is an affiliate network you work with.

For the cases where you do not work with any offer source and promote your offers, this feature can be used only if you store the data on your side and have the technical capabilities to add this data to the conversion triggered.

1. Make RedTrack identify and accept this data with a postback first.

Offer sources / Brands → Additional parameters → add the required parameters, macro, name and assign the roles → Save changes to the template:

Data MUST be added to such columns as:
◉ Macro/Token where you have to insert {r} or {replace}.
◉ Role where you assign your parameters a certain role. The list of supported roles can be viewed in the dropdown:

Data in the following columns is OPTIONAL but useful:
◉ Parameter: that’s where you give your parameter a name, but can leave it empty and in the tracking URL your parameters will be called sub1,2,3 etc.
◉ Name / Description: that’s the name you’ll see in the reports instead of sub1,2,3. For your convenience you can customize these names as you wish.

2. The added parameters will be appended to the Postback URL which you should copy:

3. Paste it to your offer source S2S postback settings as usual (or in any other postback option you use on your side).

Once the conversion postback containing those values is sent to RedTrack, we will grab it → attribute it to the appropriate campaign → send it to Facebook with the specified role.

Troubleshooting

Possible errors

Account disconnected

Missing Purchase Currency and Value Parameters

Purchase Event Missing Deduplication Parameter

Conversion attribution issues

Purchase Events May Be Dropped Due to Missing Event Source URL Parameter

Sometimes, Facebook can disconnect your account randomly for security reasons (you will notice that almost immediately since the cost data stops coming at that point). All you need to do in that case is to reconnect.

“One or more of your Purchase events is missing a value and currency parameter. This may affect your return on ad spend calculation.”

If you have the value optimization on, some conversions still do not get the value. We always send the currency and value by default. This issue can be observed with test conversions. So it’s essential to send all values during the test.

Most probably, you are using Conversion API and pixel at the same time (for example, send the same data from RedTrack and your website or use RedTrack CAPI and some other system CAPI). In this case, you might see both server and pixel type under the event in your Facebook account.
Use only the RedTrack Conversion API to solve the issue.

Another reason can be a duplicate from a pixel or Conversion API without any unique event value, Facebook can recognize. What can be done? Check out this guide.

Conversion attribution may differ due to the FB algorithms (for example, they can be sent to different adsets if Facebook considers attributing some particular conversion to another adset)

Facebook has a 7-day attribution window. If there are less than 7 days between click and conversion, Facebook will attribute it. If the conversion is older than seven days, FB can exclude it from your statistics.

You cannot do anything with the conversion attribution.

Make sure you have followed the Facebook integration guide, verified your domain, and added it to your RedTrack offer settings.

Cost update issues

No costs

Incorrect costs

Here is what you need to check on your side:

1. The traffic channel should be connected from the Facebook template. No error is shown.
If it is not connected or you are not sure, re-connect it.

2. The correct account is connected.

3. The dynamic parameters such as campaign id, adset id and ad id are received by RedTrack (Logs → Clicks → check sub values).
If there are no parameters in click logs, that means we are not receiving them from Facebook. Either these are your test clicks, or you need to check the Facebook campaign settings to have the parameters string in place.

4. The correct roles are assigned to the dynamic parameters;
For the cost update to work properly, the following roles should be obligatory assigned to the Facebook ids in your traffic channel settings:

5. Check the cost model you use in the campaign settings (should be CPC) and if the Auto-update cost toggle is on inside the campaign settings.

If, after checking/doing all the suggested actions, you still experience the problem with the costs not coming, email [email protected].

What you can check to understand why the cost data is incomplete (higher or lower than the one you have on Facebook):

1. The first thing you need to compare is the IDs. RedTrack takes the cost data per ID (campaign, adset or ad, depending on your subscription level), so if some of the ID is missing, its cost data will not be taken to your RedTrack report.

Check if all IDs are received in RedTrack (campaign report → group by (target ID used for the cost update) → check the list). If not, check this campaign, adset or ad in Facebook and ensure the dynamic parameters are added to pass the ID.

2. Check if the correct roles are assigned to the Facebook IDs in RedTrack. This can be checked in your traffic channel settings:

3. Check if the time zones match in your RedTrack account setting and in Facebook.

The timezone of the cost data received via the API can be checked in your cost logs.

If the timezones of your traffic channel and RedTrack don’t match or the timezone within your ad accounts in the traffic channel do not match (for the cases when you run traffic from different ad accounts to one RedTrack campaign), the cost data matching is impossible.

4. Check the cost logs in RedTrack: if costs stopped coming for some time and caused this discrepancy, you might need to reconnect Facebook.

5. Make sure the currency matches in both systems.

If, after checking/doing all the suggested actions, you still experience the problem with the costs not coming, email [email protected].

Lost events

Sometimes, you might need to check if there are events coming to Facebook and how they come to understand if anything goes wrong.

Business Manager → Data Sources → Datasets → choose the pixel → Open in Event Manager:

Your events are displayed under the Review:

Articles

RedTrack Chrome Plugin for Facebook Ads Manager

We'll be with you in a second