Skip to main content

Troubleshooting Data Discrepancies & Missing Ad Spend in Kickbite

Fix data discrepancies by ensuring your campaigns have the correct tracking parameters and the landing pages include the correct locale.

Written by Juan Garzon
Updated over 12 months ago

Overview

As a Kickbite user, you may occasionally see “wrong” or missing data, especially with ad spend or revenue (ROAS). This guide combines best practices for:

  • Identifying and fixing data discrepancies

  • Verifying tracking templates

  • Managing locale parameters for Meta (Facebook/Instagram) ads

  • Handling Google and Bing PMAX campaigns

  • Knowing what to do if ROAS or revenue looks too high or too low

Remember, Kickbite typically has a 1-day delay in data processing. If you see no data for “yesterday,” there may be a more significant issue with tracking, locale parameters, or ad platform integration.


Common Symptoms of Data Discrepancies

  1. Zero Ad Spend

    • Your Kickbite dashboard shows no spend for certain campaigns, ad sets, or ads, even though the ad platform confirms that spend exists.

  2. Partially Missing Data

    • Some ad sets or campaigns display correct spend, while others do not—even within the same account.

  3. Incorrect ROAS/Revenue Figures

    • The reported revenue appears abnormally high or too low compared to other analytics platforms.


Step-by-Step Troubleshooting

1. Identify Your Campaign Details

  • Pinpoint which campaign(s), ad set(s), or ad(s) are affected and which market or locale they target (e.g., DE, US).

  • Gathering this information helps you track down where the discrepancy begins.

2. Check the Data Refresh Delay

  • Kickbite data generally updates once per day.

  • If you’re missing data for ads that ran yesterday, it often indicates a bigger data processing issue.

  • Make sure 24 hours have passed since the ads ran before concluding that data is truly missing.

3. Verify Tracking Templates

  • Many data quality problems stem from incomplete or incorrect tracking templates.

  • Compare the tracking template of any problematic campaign(s) with another campaign that’s reporting correctly.

  • If you’re unsure how to check or update these, see our Academy article,
    “Keep your data clean using Kickbite’s Tracking Templates!”

4. Confirm Landing Page & Locale Parameters (Especially for Meta)

  • In catalog or Dynamic Product Ad (DPA) campaigns, each ad set may have different landing pages.

  • Kickbite must detect parameters such as /de for German pages (or /en for English) to map ad spend correctly.

  • Missing or incorrect locale parameters can result in zero-reported spend.

Example

Tip: If you’re targeting multiple countries or languages, ensure each ad set’s URL includes the correct locale for its audience.

5. Examine Revenue/ROAS Discrepancies

  1. If Your Revenue/ROAS Seems Too Low

    • Many ad platforms (e.g., Meta, Google) can overestimate campaign performance by ignoring the multi-channel nature of the customer journey.

    • Check Kickbite’s “Marketing Channels” view to compare different attribution models (e.g., lifetime click & view - maximum amount of conversions the channel has without considering synergies to other channels).

    • If numbers remain suspiciously low after investigating various attribution windows, contact Kickbite Support for further assistance.

  2. If Your Revenue/ROAS Appears Too High

    • Kickbite’s tracking can attribute longer customer journeys (beyond cookie-based methods), which may inflate aggregated revenue.

    • If the numbers seem unrealistically high, contact Kickbite Support to review user-matching data and attribution windows.


Additional Guidelines (Google & Bing) and special case for PMAX

In Google Ads, tracking parameters are typically set at the campaign level. But be careful—if you’ve also added templates at the ad group or ad level, they can override the campaign-level settings. This can lead to tracking conflicts, especially if Kickbite parameters are involved. To avoid data issues, always check the lowest level where tracking templates might exist.

If you’re running Google or Bing PMAX campaigns (Performance Max) and notice incorrect or missing ad spend, apply the following tips:

  1. One Ad Account = One Market

    • If your account is dedicated to only one market, you generally won’t have any problems.

  2. One Ad Account = Several Markets (With PMAX)

    • If your single ad account serves multiple markets and you run (or plan to run) PMAX campaigns:

      • Make sure you include a market identifier in the campaign name (at the beginning or the end).

        • Example: DE_PMAX_campaign or PMAX_campaign_DE

      • The market identifier must match exactly how the market is named in Kickbite.

        • If Kickbite uses DE, don’t use DACH in the campaign name, or Kickbite won’t map the data correctly.

  3. Tracking Templates in Bing (for PMAX)

    • For Bing PMAX campaigns, ensure you remove the ad group ID from the tracking template.

    • Only the campaign ID should remain in the tracking URL parameters.

    • This is crucial for Kickbite to attribute spend to the correct campaign and market.


How to Fix Missing Meta Ad Spend

  1. Check Tracking Parameters

    • Verify that each Meta ad or ad set includes the same Kickbite tracking parameters (detailed in our Academy article).

  2. Include the Correct Locale

  3. Allow Time for Data Sync

    • After making any URL or parameter changes, wait for the next Kickbite refresh cycle (usually the next day) to see your corrected spend data.

Need Additional Support?

If you’ve followed these steps and still don’t see the correct data—or you need more personalized help—reach out to human support. Be prepared to provide:

  • Campaign or Ad Set IDs

  • Timeframes

  • Screenshots of your tracking templates and landing page URLs

  • Confirmation that you’ve waited 24 hours for the data to refresh

With these details, our support team can more quickly diagnose and resolve the issue.

Article last updated: April 11, 2025

Did this answer your question?