Troubleshooting and FAQ

If no data appears in Tracklution after installation, follow these steps:

1. Verify event tracking – Visit your website and check if the event appears in Tracklution, if nothing happens, the installation is not done correctly.
2. Check your integration settings – Ensure that the scripts in your code / Google Tag Manager, or WooCommerce / Shopify settings match exactly with the installation instructions. You can revisit your unique installation instructions from the "installation" page on your Tracklution Dashboard.

If some events are missing in Tracklution, check the following:

• Ensure the tracking script loads at the beginning of the page
• Load the main script before event scripts – The primary tracking script must be initialized before event-specific scripts.
• Use webhooks for additional tracking – Some events cannot be tracked with scripts alone. Use webhooks to enrich event data in Tracklution.

If your DNS verification is still pending, consider the following:

• CNAME format may vary – Some platforms require just "tralut", while others may need "tralut.YOUR-DOMAIN-HERE.com". Test both options for CNAME.
• Allow sufficient propagation time – DNS updates can take up to 48 hours to fully propagate.

Check the code 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 setup 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 correct code:

<script>
  tlq('track', 'Purchase', {value: 2.25, currency: 'EUR'});
</script>

For more information about the "Purchase" event, see the Tracking Events section.

To verify if the Tracklution tag is loading in your browser, follow these steps:

1. Open your website in a browser.
2. Right-click anywhere on the page and select Inspect (or press F12 / Cmd + Option + I).
3. Navigate to the Network tab.
4. Refresh the page.
5. In the search bar, type "tralut".
6. If the Tracklution tag is loading correctly, you should see related network requests appear.

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, check the following:

• Turn on the "Wait for tags to load" setting for your trigger (if the trigger has this setting). Your setup should look like the reference screenshot below:

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

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:

1. Refer to our debugging guide – See our troubleshooting guide here. The article explains how you can quickly check what events are tracked, not tracked, delivered and not delivered to your Connectors, and why.
2. Allow time for data sync – If you recently connected your ad platform to Tracklution:
   • Most platforms: Wait 24 hours and check again.
   • Google Analytics 4 (GA4): May take up to 48 hours.
3. No action needed for re-delivery – Tracklution automatically attempts to re-deliver conversions that encountered errors.

If the error persists beyond 48 hours, check the error code in our guide or contact support for assistance.

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.

✅ Solution: 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.

1. Open your Tracklution Dashboard (the front page of Tracklution)
2. Click on the Google Ads connector card to filter the dashboard and display only events with Google Ads as the source.
   
3. Scroll down to the data table below the graph.
4. Open any session that contains an event you’ve sent to a connector (e.g., Purchase).
   • You can filter events by searching for the event name in the search bar.
5. Click the arrow on the session to view the status of delivery.
6. If an error appears, open the payload from “View” and locate the error code.
   What the error can look like:

If you encounter an error, refer to the common Google Ads issues below.

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, try changing your Enhanced Conversion settings from Google Tag / Tag Manager to API.

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

1. Go to Google Ads and open the sub-account previously connected to Tracklution.
2. Navigate to Admin → Access & Security → Managers.
3. Remove Tracklution from the existing manager connection.
4. Reconnect Tracklution to the correct MCC account.

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.

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!

If the list that shows the error is the Click conversion list (not 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!

• Purchase Click conversion is a a conversion that has been delivered to Google Ads and the session has a Google Click ID.
• Purchase View-Through / Engagement Conversion is a conversion that has been delivered to Google Ads, but the session does not have a Google Click ID, but it recognizes the conversion otherwise (e.g. the user has seen a YouTube ad, by which it is identified).
• When comparing to another setup, these should be added together, as usually those are not separated.
• Both lists should be used as primary.

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"

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 may overattribute sales if Google is marking the conversion for the day when the click came and Tracklution to the day when the purchase was made.

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 Coversion 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. Solution: Ensure that either the Meta Pixel or Tracklution handles event tracking, not both. Disable duplicate tracking to avoid inflated data.

• Make sure all events are approved, especially custom events might have to be separately approved in Events Manager before they start working
• Make sure that in your pixel in Meta, you have your domain as an allowed domain
• Check Diagnostics page for any errors

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:

• Top of funnel events (e.g., PageView) → 5-6 is a good score.
• Bottom of funnel events (e.g., Purchase, Contact form submission) → 8-10 is ideal.
• A perfect 10 is rare because some identifiers, like FB Click ID, are unlikely to be present in all conversions.