GTM template with instructions video from Simo Ahava!
Are you missing an event that should be delivered to Meta or Google Ads? Find your missing event by going through the Tracklution Debug Quest.
If no data appears in Tracklution after installation, follow these steps:
If some events are missing in Tracklution, check the following:
If your DNS verification is still pending, consider the following:
Check the script for the "Purchase" event on your website. Are the values for "value" and "currency" setup correctly? If you are using a variable for the value, make sure that the variable is set up correctly. If you are passing data to the "tlq" function call, make sure that the data is setup correctly. **If you hard-code the value for these fields, they will remain the same for every event sent. So they need to be filled dynamically by the code on your website.**E.g, if you want to send the sum of the purchase in the "Purchase" event, you need to pass the sum to the "tlq" function call correctly from your system. Example of Purchase script in GTM:
To verify if the Tracklution tag is loading in your browser, follow these steps:
Open your website in a browser.
If no results appear, double-check your installation settings.
If an event is visible in Google Tag Manager’s (GTM) debugger but is not loading in Tracklution, it most likely means the tag does not have time to load in the live environment. If the trigger allows, turn on the "Wait for tags to load" setting for your trigger. Your setup should look like the reference screenshot below:
Most causes for problems can be found from Tracklution Dashboard, which is an excellent tool for debugging. Please familiarize yourself with our debugging guideguide or the video in the beginning of this article. The article explains how you can quickly check what events are tracked, not tracked, delivered and not delivered to your Connectors, and why.
Tracklution determines conversion sources based on the ClickID and attributes conversions on a last-paid-click basis. This means the last paid ad click before a conversion gets credited, if Tracklution tracked a ClickID. **However, all conversions are still sent to ad platforms, allowing them to apply their own attribution models within their respective attribution windows.**This ensures platforms receive multiple conversion signals, optimizing ad performance through their algorithms. Please check our article about Attribution.
If you suspect incorrect attribution, check your ad platform's attribution settings to compare how conversions are credited.
If you encounter an error related to ad platform data delivery, follow these steps:
This is often due to over-attribution by ad platforms. Platforms like Meta and TikTok may assign credit to view-through conversions, especially if an ad was shown shortly before a user converts via another channel. To solve this; consider adjusting your attribution settings. For example, switching to a 1-day click attribution model in Meta often provides a more realistic view of ROAS.
The Microsoft Entra (Azure AD) tenant must have the Microsoft Advertising API service principal registered. This is a prerequisite before any user in that tenant can consent to apps requesting Microsoft Advertising API permissions. The admin needs to create the service principal for Microsoft Advertising API in their tenant.
The error can appear if the lists are for Click conversions (not Conversion Booster / view through conversions). Click conversions are delivered with the CAPI from Tracklution, and thus the tag is never loaded - as it is not supposed to be loaded. This error can be ignored.
If the list that shows the error is the Click conversion list (not Conversion Booster / View through conversion list) it is normal to get that error. Tracklution does not upload contact info for conversions with a click ID; all of those go to the View through conversion list as enhanced conversions. This is normal and requires no action.
The error can appear if the lists are for Click conversions (not view through conversions). Click conversions are delivered with the CAPI from Tracklution, and thus the tag is never loaded - as it is not supposed to be loaded. So this error can be ignored!
The setting needs to be edited in Google Ads, once it's done, Enhanced Conversions will be toggled on automatically in Tracklution. To change the settings in your Google Ads account, go to: Conversions, Settings, Turn on enhanced conversions for leads. Activating this feature is advised for enhanced conversion attribution in Google Ads. Make sure you are editing "Enhanced Conversions for Leads" setting, not "Enhanced Conversions".
After correctly enabling Enhanced Conversions in Tracklution and Google Ads, Tracklution can still show higher number of delivered conversions than what is reported in Google Ads. Tracklution shows "Success" for the event status (more about event statuses here) if an event was successfully sent, regardless of whether Ads decides to use it for reporting. Google Ads only shows the subset that it has successfully attributed to a click or impression. It's possible to have a big number of conversions that Tracklution was able to send to Google as Enhanced Conversions, but Google did not attribute those because these people have not seen an ad.
If you notice a drop in Google Ads quality score or see the following error:
"Enhanced conversions configuration does not match upload type"
This can be caused by affiliate traffic where the ClickID does not belong to your ad account. If you do not use affiliate links, ensure your Enhanced Conversion settings are using Google Ads API as the method.
If you see the following error in Google Ads:
"Can't import events to a conversion action that was just created. Try importing again in 6 hours."
No action is needed. This occurs because Google Ads requires a short delay before accepting new conversion actions. Tracklution will automatically re-deliver conversions, so the issue should resolve itself within 6 hours.
If you see an orange “N” next to a Google Ads logo in the event log, it means the click match failed; either because the Google Click ID (GCLID) or the enhanced data (like email) was missing or invalid. You can check the exact reason in the event's payload details. The "N" just marks a normal, expected error. If the error reason was enhanced conversions, ensure you've set those on.
If you see this error:
"The Manager and sub-manager to be linked have duplicate client."
This means you are trying to connect a Google MCC account that already has a linked child account in Tracklution. To solve the issue:
After completing these steps, you should be able to re-establish the correct connection.
If you encounter this error:
"The imported GCLID could not be decoded. Make sure you have not modified the click IDs."
Check the ClickID of the session. This error can occur when affiliate traffic or external sources send traffic with ClickIDs that do not belong to the Google Ads account that you have connected to Tracklution.
Data can be delivered fully server-side to Google Ads through API if wanted, as long as there is GCLID. The setting is found from the Google Ads connector settings when you scroll the page to the end.
Google is marking the conversion for the day when the click came and Tracklution to the day when the purchase was made so these numbers will never fully match.
Most probably you see too many conversions in your reports because you have multiple Conversion action lists as 'Primary' goal. it is recommended to only have 'Tracklution - Purchase Click Conversions' and 'Tracklution - Purchase View-Through / Engagement Conversions' lists as Primary.
First make sure you have created a conversion action list for Google Ads. Click "edit" on the Google Ads connector card and then "Create Conversion Action" next to the event you want to deliver to Google Ads. You can only deliver conversions to Google Ads if they have GCLID.
If you want, you can use Tracklution generated Conversion Action lists as “Secondary” (action optimization column) - then Google will just monitor, not use the data for optimisation yet. When you see that all works as expected, you can switch Tracklution as primary and the previous conversion list as secondary.
Tracklution tracking will work with Google Tag Manager instead of Google Ads API, but you'll miss enhanced conversions (affecting usually around 2-20% of your tracking). Switching to Google Ads API ensures enhanced conversions, but other Google Tag Manager tracking may lose enhanced conversion data.
If you have the Meta Pixel installed before setting up Tracklution, you may be tracking duplicate events. To fix this, ensure that Tracklution is the only source of data for the Pixel. Tracklution handles both pixel and CAPI.
If you have ensured that Tracklution is the only source of data to that Pixel in Meta (no other tags bringing data to that Pixel), in some places in Meta it might still look like the events are appearing as double in Meta Events Manager. To ensure your setup is correct;
Meta can attribute a large number of view-through conversions to its campaigns, particularly when an ad is shown to a user shortly before they convert via another channel. If this discrepancy is a concern and you’d like to adjust for it, I’d recommend reviewing Meta’s attribution settings. In our experience, customers who have encountered over-attribution issues in Meta have found that switching to a 1-day click attribution model results in a more realistic ROAS.
Meta's Conversion Match Quality score can be low due to insufficient customer data signals, missing identifiers (like email or phone), or poor data formatting. Improving data accuracy and adding more customer identifiers can enhance your score. Make sure that you send the identifiers to Meta, and that those are accepted in Meta Events Manager after Tracklution sends the conversions.
Benchmark Guidelines:
The fbc parameter is Meta’s click identifier. It is generated when a user clicks a Meta ad and lands on your site. The value is first stored in the browser and then captured and stored in Tracklution’s session data, allowing it to be used for server-side conversion delivery.
Even so, fbc is often missing at conversion time. Meta might not always be the most frequent last-paid-click channel, and many users convert later through direct traffic, Google, or another channel. In addition, Meta traffic frequently comes from Facebook and Instagram in-app browsers, where privacy restrictions and short cookie lifetimes limit how often fbc is available.
A low fbc rate is normal and does not indicate a tracking issue. Tracklution can still send conversions to Meta using server-side delivery and other matching signals when the click ID is not present.
In Meta Events Manager (NOTE, not Ads Manager). Open the Pixel that Tracklution is delivering data to, open the event details and find the event volume graph under "Event overview". Compare the "Total browser events received & Total server events received" to the reflective day(s) in Tracklution dashboard (Delivered to: Meta). Tracklution deduplicates the conversions its sends from CAPI & pixel automatically - so if you see 100 events delivered from Tracklution to Meta (from the Tracklution dashboard), you should also see approximately 100 browser events and 100 server events received by Meta.
Events Manager lists all events Tracklution sends to your Meta pixel, regardless of whether Meta decides to use them for ad reporting. Ads Manager only shows events that are attributed to your ads according to Meta’s attribution model and settings (e.g., attribution window, matching rules, campaign connection). So, if the events appear in Events Manager but not Ads Manager, it means that Tracklution is working correctly, but it is possible that:
Sometimes you may notice that GA4 reports more traffic and conversions under “Unassigned” after implementing Tracklution tracking. This is linked to how GA4 identifies sessions. GA4 requires a unique client_id (also called GA4ID) for every session. This ID is only created if GA4’s own script (gtag.js) loads successfully in the visitor’s browser. If the script never runs, the client_id doesn’t exist. Tracklution creates a dummy client_id when GA4’s script hasn’t provided one. This ensures all events can be forwarded to GA4, so you should now see all sessions delivered in Tracklution.
However, when GA4 receives events with a dummy ID, it cannot connect them back to a real browser session. GA4 still logs the conversions, but often attributes them as “Unassigned” traffic. This explains sudden increases in Unassigned numbers.
Why GA4’s script might not load? There are several reasons why GA4’s client_id isn’t generated:
Why Tracklution sees more than GA4?
Because Tracklution runs server-side in a first-party environment, we can still capture the event even if GA4’s script is blocked. That’s why you may see a session and conversion in Tracklution, but GA4 attributes it as Unassigned. It is normal for 1–10% of sessions to be affected by this, depending on industry and audience. In privacy-heavy industries the percentage may be higher, as more users block Google’s scripts.
Server Side Tracking
Google Ads Server Side Tracking
Facebook Server Side Tracking Connector
TikTok Server Side Tracking
Shopify Server Side Tracking
GA4 Server Side Tracking
LinkedIn Server Side Tracking
Snapchat Server Side Tracking
WooCommerce Server Side Tracking
WordPress Server Side Tracking
Pinterest Conversions API
Microsoft (Bing) Server Side Tracking
Stripe Conversion Tracking


4.8+ Rating on G2 and Trustpilot
Helsinki
Simonkatu 6 A
00100 Helsinki, Finland
New York
307 W 38th St
NY 11105, United States



© Tracklution Oy 2026. All rights reserved.
GTM template with instructions video from Simo Ahava!