What gets reported
Kompare follows a reader through your widgets and reports each step to the platform you connected. Events are sent from Kompare's servers, so you do not have to change anything on the travel agency's site.
- Search: the reader searched for a trip
- Trip opened: the reader looked at a specific trip
- Click to the travel agency: the reader left to book
- Checkout started: the reader opened the agency's checkout, where the agency's checkout start is set up
- Purchase: the booking was confirmed
Consent comes first
Kompare reads the consent choice from your cookie banner, including the common consent tools and Google Consent Mode. It sends events only for visitors who have agreed to marketing. If a visitor has not chosen, or Kompare cannot tell, the answer counts as no and nothing is sent.
For visitors who did consent, events can include technical identifiers such as the IP address, which the platforms use to match an event to an ad click.
Google Ads needs the visitor to have arrived from one of its ads, so it receives events only for those visits. Meta and TikTok can also match other consenting visitors.
Connect, test and keep an eye on it
You connect each platform in your console. For Meta and TikTok you add details from your own account. For Google Ads you sign in with Google and choose a conversion action for each event.
In test mode Meta and TikTok show the events in their own test view, and validating the connection sends them a test event and shows you the result. For Google Ads, test mode and validation check the events without recording anything. The log then shows, for 7, 30 or 90 days, what happened to each event: it reached the platform, it was held back, or it needs your attention.
A Purchase is sent when the booking is confirmed, without waiting for the travel agency to approve it, and it is dated by the sale. Its value is your commission on the booking, not the price of the trip. Events are not withdrawn if a sale is later cancelled or disputed.
Kompare connects to these platforms but is not affiliated with or endorsed by them.
- Held back: no marketing consent from the visitor
- Held back: for Google Ads, the visitor did not come from one of its ads
- Held back: the event is too old for the platform to accept
- Held back: no conversion action chosen for that event

