Meta and RedTrack

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

Pixel and Conversions API tracking covers standard accounts well. Most limits here come down to your niche or account type, and several are controlled by Meta, not by RedTrack.

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. Add the integrated domain to your RedTrack account → activate the Free SSL toggle.

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 in the offer source settings to send conversion data back to RedTrack.

The parameter with the External ID role must be configured in the Offer source form.
Meta recommends having this parameter with the CAPI for better attribution.

The value sent to the Meta Pixel depends on how this parameter is configured:
– If a parameter is assigned the External ID role, that means you need to send it to RedTrack with the conversion; that value is sent to the Meta Pixel in the external_id field.
– If no parameter is assigned the External ID role, or the parameter has no value, the system sends the “RedTrack clickid” in the external_id field by default.

Your Offer source → Additional parameters → assign the External ID role to the parameter:

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

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.

The parameter with the External ID role must be configured in the Brand settings.
Meta recommends having this parameter with the CAPI for better attribution.

The value sent to the Meta Pixel depends on how this parameter is configured:
– If a parameter is assigned the External ID role, that means you need to send it to RedTrack with the conversion; that value is sent to the Meta Pixel in the external_id field.
– If no parameter is assigned the External ID role, or the parameter has no value, the system sends the “RedTrack clickid” in the external_id field by default.

Your Brand → Additional parameters → assign the External ID role to the parameter:

3. Go to Websites → New → Add your website URL (this is your e-commerce shop/website link).

1. Traffic Channels → New from template → Meta → Add → Save:

PAY ATTENTION TO THE ADDITIONAL PARAMETERS SECTION:

Blocked (greyed) parameters

“fbclid” parameter

sub 19 & sub 20

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 Meta. This parameter should always be the last in the line, meaning that there should be no other parameters when you add the parameters string to Meta:

DO NOT edit sub 19 or sub 20 parameters in the template, since they have the hardcoded fbp and fbc in these places.

• fbp identifies a visitor’s browser session when they come to your site from Meta.
• fbc stores the Meta Click ID when a user clicks a Meta ad, allowing attribution back to that ad.

The Meta Conversions API requires these parameters, and they must stay in their exact format. Altering them can disrupt attribution, leading to inaccurate tracking and unreliable reporting.

Learn more about these parameters by following this Meta article.

2. In the added template:

• Go to Meta API Integration section → Connect Meta → verify your ad account:

• Once you are redirected to your RedTrack account settings and see the Connected button, it means Meta accepted the integration → Save changes to the template:

3. Enable Impression cost sync if you want RedTrack to record Meta costs when ads receive impressions and spend but no real clicks:

• Enable the Impression cost sync toggle → add your Meta Ad Account ID in the act_12345 format → Save:

Creating a campaign in RedTrack

To create a campaign in RT act, depending on your account type:

I’m Affiliate

I’m Advertiser

Campaign for the paid traffic (mandatory)

Campaign for the organic traffic (optional)

Campaigns → Create new campaign → 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.

To track organic clicks alongside your paid traffic, set up a dedicated campaign for the organic traffic.

Campaigns → Create new campaign → use this guide to help you set up campaign for the organic traffic.

2. Once the Campaign is saved, go to Tracking links and parameters → copy the corresponding tracking parameters and the script depending on tracking method you decided on:

Redirect URLs are generally not allowed on Meta unless you have confirmation from Meta.
Therefore, we strongly recommend using the no-redirect tracking method (either with the Universal Script or the No-Redirect).
– Use Universal Script when you’re working with the same landing page across multiple traffic channels.
– Use No-Redirect Script when you’re working with one landing page and one traffic channel.

IMPORTANT!
– If you choose the simple No-Redirect option: once the campaign is saved, both the tracking parameters and the script are generated automatically. You only need to copy and apply them.
– If you choose the Universal Script option: once the campaign is saved, only the tracking parameters are generated automatically. You’ll need to create the universal tracking script manually – follow this guide.

3. Apply Script & Parameters.

• Paste the script into your landing page code.
• Add the tracking parameters to your Meta campaign (see Step 7 “Create an ad on Meta” of this guide).

1. Campaigns → Create new campaign → 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. Once the Campaign is saved, go to Tracking links and parameters → copy the tracking parameters from the Tracking parameters (UTMs) tab:

The universal tracking script was automatically created once you added the Website in RedTrack. Follow this link to find all the created universal tracking scripts within your account.

3. Apply Script & Parameters.

• Paste the script into your landing page/website code.
• Add the tracking parameters to your Meta campaign (see Step 7 “Create an ad on Meta” of this guide).

Special case: redirect tracking and fbc,fbp parameters

When using redirect tracking with Meta, the fbc and fbp parameters are not captured by default. This leads to incomplete data tracking.

To make it work, act as follows:

1. burger menu → Settings → enable the toggle Redirect for Meta → Save changes:

2. Place the following script on your landing/website at the end of the body:

<script src="https://{{domain}}/clickupd_fbp_fbc.js" defer></script>

In your Meta account, copy the following:

Conversion API key (access token)

Pixel ID

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

Here is more about the Conversion API Key in Meta.

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

Now in your RedTrack account, you should:

• Set up Meta pixel (add the copied Pixel ID & Conversion API Token to CAPI Integrations, configure custom conversion matching, define payout values, etc.)
• Assign the added pixel details to either the Facebook traffic channel or your offer/website.

1. RedTrack → CAPI Integrations → Meta → Add New:

2. Fill in the mandatory fields → Save:

Title

Pixel ID

API key

Default event payout customisation

Event URL

Action source

Data Quality API Token

Conversion matching & payout customization

Give your pixel a name to distinguish it from all the other added pixels.

That’s where your Meta pixel goes.

That’s where your Meta access token goes.

1. Add Default event name

Here goes the event name for the default conversion in RedTrack, when no type= is used in the postback or no conversion name information is sent to RedTrack:

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.

2. Set up a payout customisation

Payout customisation for the Default event name (default conversion type) serves to control the financial data associated with this conversion event.

You can define a concrete payout type and value that RedTrack will associate with that conversion event when reporting to Meta.

Remember that when setting up Payout customisation at this stage, you configure it for the Default event name.

Since you can define a payout value for both the Default event name and the events in the Custom Conversion Matching section, you should know that if the payout type is configured for the same event in both places, the settings in the Custom Conversion Matching section will take priority.

How to set up payout customisation

Press Add payout customisation → select the Payout type → define the payout value for the default event:

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.

This is the URL where the event occurs. Use the https://domain.name URL structure.

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

About Meta domain verification

Why verify your domain in Meta

Meta no longer requires mandatory domain verification for configuring web events, however, it is highly recommended.

Why it’s still highly recommended:

• Grants control over link-preview editing via Meta’s Brand Safety.
• Secures your domain so only verified Business Managers can claim/configure it.
• Improves tracking reliability (especially for Pixel + CAPI setups) by preventing ownership conflicts.

Risks if you skip verification:

• Another Business Manager might claim your domain and take over event setup.
• You may lose control of how link previews appear in paid and organic content.
• Attribution may be less stable/accurate when using server-side events + Pixel without verified ownership.

 How to verify your domain in Meta

Domains on Meta 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 Meta

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 Meta 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:

This is where your event originates from. We recommend using the Website option.

Data Quality API Token allows RedTrack to access Meta’s Dataset Quality API for your Pixel/Dataset. It is used to sync EMQ Score metrics so you can monitor Pixel performance directly in RedTrack.

To generate it, go to Meta Events Manager → select your Pixel/ Dataset → Settings → Set up direct integration → Set up with Dataset Quality API → copy and paste it into the Data Quality API Token field in RedTrack:

To be able to view the EMQ score in RedTrack, enable the Custom Conversion Matching toggle and choose the conversion type and event name.

We recommend keeping a Purchase name for one of your conversions so you don’t need to make any adjustments on the Meta side. Meta knows this name well and will optimize traffic better for a Purchase than a custom name (Sale, Conversion, etc.).

By default, the system automatically sends your conversions via CAPI exactly as you name them, but conversion matching lets you control how they are sent to Meta.

To set up conversion matching, act as follows:

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 will send to RedTrack.

2. Enable the Custom Conversion Matching toggle in the pixel settings → match the events from the Conversion Type column with the events from the Event name column:

Under the Conversion Type column, you select the events added in RedTrack.
Under the Event name column, you select Meta’s event names.

You can skip that step if you use only the Meta standard event names.

3. Set up Payout customisation for the matched events.

The Payout type, Value block and the Postback when conversion payout block do not conflict with each other. They can function independently or together, depending on how you want to control your reporting.

You can configure either block on its own, or both at the same time:

Scenario 1: You decide to set EITHER Payout type & Value OR Postback when conversion payout. In that case, look for the examples of how that works out in the blocks below.

Scenario 2: You decide to set up both Payout type & Value AND Postback when conversion payout. In that case:
* Postback when conversion payout controls which conversions are allowed to be sent to Meta.
* Payout type & Value controls what payout value will be sent for those conversions.
Thus, in scenario 2, first the postback condition decides whether a conversion should be forwarded → then, the payout customisation decides what payout amount is included in that conversion when it is sent.

3.1 Payout customisation → Payout type & Value

Why use payout customisation

Payout customisation for the matched Conversion Type & Event Name controls the financial data associated with this conversion event. You can define a concrete payout type and value that RedTrack will associate with that conversion event when reporting to Meta.

Since you can define a payout value for both the Default event name and the events in the Custom Conversion Matching section, you should know that if the payout type is configured for the same event in both places, the settings in the Custom Conversion Matching section will take priority.

How to set up payout customisation

Press Add payout customisation → select the Payout type → define the payout value for the matched event:

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

What’s given:

You receive 3 conversions with different payouts:

• Conversion 1 → $20
• Conversion 2 → $10
• Conversion 3 → $30

Payout setup example 1:

What it means:

You want every conversion sent to Meta with a fixed payout of 40, regardless of its actual payout.
RedTrack ignores the original payout and replaces it with 40 for reporting.

Outcome for payout setup example 1:

• Conversion with $20 → sent as 40
• Conversion with $10 → sent as 40
• Conversion with $30 → sent as 40

 

 

Payout setup example 2:

What it means:

You want to send 50% of each conversion’s actual payout to Meta.
RedTrack calculates half of the real payout and uses that number for reporting.

Outcome for payout setup example 2:

• Conversion with $20 → sent as 10
• Conversion with $10 → sent as 5
• Conversion with $30 → sent as 15

 

 

3.2 Payout customisation → Postback when conversion payout values

Why set up a conditional postback for the matched events

This feature provides control over the conversion data shared with your Meta pixel by adding a financial filter for each matched conversion type. By defining specific payout or revenue thresholds, you ensure that only high-value or desired conversions are used by Meta’s ad optimization algorithms, while all conversions are fully tracked in RedTrack.

Since you can define a payout value for both the Default event name and the events in the Custom Conversion Matching section, you should know that if the payout type is configured for the same event in both places, the settings in the Custom Conversion Matching section will take priority.

How to set up a conditional postback for the matched events

To activate this feature, press Payout customisation next to the matched events → select the Postback when conversion payout measurement and define the value for it:

Select the logical relationship that must be true between the conversion’s actual payout and the specific value. The options govern how the system filters the conversion:
* Higher than: The conversion is sent only if its payout is strictly greater than the specific value.
* Less than: The conversion is sent only if its payout is strictly smaller than the specific value.
* Equals: The conversion is sent only if its payout matches the specific value exactly.

The system will check if the conversion meets the selected criteria:
– If it does, the conversion will be sent to the Meta pixel.
– If it does not meet the criteria, the conversion will not be sent to Meta, though it will still be registered in RedTrack.

Example

What’s given:

You receive 3 conversions with different payouts:

• Conversion 1 → $20
• Conversion 2 → $10
• Conversion 3 → $30

Setup for Postback when conversion payout:

What it means:

Only conversions with a payout above 15 will be sent to Meta via CAPI.
Conversions with a payout of 15 or lower will stay in RedTrack but won’t be forwarded.

Outcome in this setup:

• $20 → sent
• $10 → not sent
• $30 → sent

So, only conversions 1 and 3 match the rule and are forwarded to Meta.

 

Once the pixel is added, you can check its connection/ the EMQ score/ edit/ delete it:

3. To assign this pixel: View details → select Traffic channel or Websites → Add new → select destination → Save:

4. Click View EMQ score to see Event Match Quality metrics from your Pixel without switching to the Meta interface:

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

1. Once you’re done with the integration and have created a Meta 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.

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.

Set up the automation:

• Use this guide to help set up automated rules.
• Use this guide for setting up the auto-update cost feature.
• Here is how Ads Manager operates in redTrack.

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 Meta.

It does not take any additional values from Meta, 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.

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 Meta with the specified role.

No 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 mandatorily assigned to the Facebook IDs in your traffic channel settings:

5. Check the cost model you use in the campaign settings. It should be CPC.

Incorrect costs

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

1. Missing Facebook IDs in RedTrack

2. Incorrect role assignment in traffic channel Settings

3. Time Zone mismatch between RedTrack and Facebook

4. Cost sync issues

5. Currency mismatch between platforms

6. Duplicate click costs due to Meta “Site Links” feature

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.

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

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.

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

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].

Issue:
RedTrack click costs are 2–3x higher than expected.

Cause:
Meta recently introduced a “Site Links” feature that is enabled by default on new campaigns. When active, this feature:

• Automatically adds multiple landing page links to your ad.
• Redirects traffic to multiple URLs, each potentially associated with different campaign or ad IDs.

As a result, the same click can be logged multiple times across different RedTrack campaigns, inflating reported cost and traffic metrics.

How to Identify It:

→ In RedTrack, look for duplicate Adset IDs across active and paused campaigns.
→ Check your UTM parameters. If you see something like sub9=facebook-SiteLink, this feature is likely enabled.

Solution:

Go to your Meta ad settings → navigate to the Ad Creative section → under Creative Setup disable the Apply site links toggle → Save your changes and monitor if the duplicate tracking stops:

Disable Site Links unless you intentionally want to split traffic across multiple landers. Also, consider updating your ad templates to prevent them from turning on by default in new campaigns.

If you’re having trouble locating the Site Links toggle or navigating specific Meta Ads settings, please contact Meta Support directly.

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: