An integration is a deeplink or widget integration that leads to the GetYourGuide website.
Q: How does the integration analyzer script find integrations?
The integration analyzer script searches all the webpages where it’s been installed for GetYourGuide integrations. All of the integrations the script finds are thenshown in a table on the analytics page of the partner portal.
The integration analyzer script activates whenever a user comes to a webpage with a GetYourGuide integration. All your integrations on that page get a view.
When the user clicks on one of your GetYourGuide integrations, the script is activated again, giving that integration a click.
If the user books a tour after clicking one of your integrations, the script is activated once more and that integration gets a booking.
Q: What’s a view?
Any time the user comes to your page all the integrations to GetYourGuide installed on that page receive a view. If the same user visits the same page again or reloads the page, the integration(s) register 2 views.
Q: Does it matter if the user actually sees the integration (i.e. does the integration have to be inside the user’s viewport)?
No. Even if the integration isn’t seen by the reader (i.e. the page was loaded but they did not scroll down to see it) the integration will still receive a view. Every integration on the webpage receives a view every time a user visits.
Q: What’s a click?
Any time a user clicks an integration, that integration will get a click in the integrations table. If the same user clicks the same integration twice, that integration will have 2 clicks in the integrations table.
Q: What does CTR stand for?
CTR = Clicks / Views
CTR means click-through rate. This metric shows how likely your integration is to be clicked. Placing integrations higher on the page, highlighting them and giving additional reasons for the users to click them can increase your integrations’ CTR, increasing the likelihood of selling something via GetYourGuide and earning commission on the customer’s booking.
Q: What’s a booking?
A booking is counted in your integrations table every time a user makes a booking on GetYourGuide having come through to the site from one of your integrations. One booking is always one activity booked by a customer. If the customer books 2 activities coming from one link, you will see 2 bookings on the integrations page.
Q: What does CR stand for?
Conversion Rate = Bookings / Clicks.
CR means Conversion Rate. Conversion Rate shows how likely the customer is to buy a tour after clicking an integration.
Conversion Rate can depend on different factors: the quality of the tour being sold, the number of reviews on the tour, price of the tour and customers coming through your integration. The higher the Conversion Rate, the more customers are buying the tour, and the more you are able to earn.
Q: Are you using a cookie attribution model for the integrations page?
No, in the Integrations table we are using the last-click attribution model.
It means that after a user clicks on an integration –> they should book an activity directly. If they don’t book an activity but come back to GetYourGuide in a few days and book an activity, you will not see their booking in your integrations table.
Unfortunately, we currently cannot use the 31-days cookie attribution model to show you performance per integration.
However, the intent of this page is for you to be able to compare different integrations and their performance relative to each other.
| Important: This doesn’t impact your commission in any way. You will get full credit for any booking (cookie-based) within 31 days after a user clicks on one of your integrations. |
Q: What happens when I remove an integration from one of my webpages?
If you delete an integration, it will disappear from the integration table with all the corresponding data.
Make sure to store the data for the links that you are deleting if you need those, as they will not be displayed on the integrations table once you remove them from your website
Q: What does “total integrations” mean?
Total integrations shows how many integrations with GetYourGuide the script has detected on your website.
Q: How do I fix broken and redirected integrations?
To fix the integrations you need to change them. Find the broken integration on your website by going to the URL location that we highlight for you and change the broken integration for a correct link. For redirect integration – consider whether changing it is appropriate or not. See next section.
Q: Do I have to change all links marked as redirected?
No, sometimes tours get back live in a day, sometimes in months. If the link is redirected – do not rush to changing it to something else. Read through why that can happen (maybe the attraction is closed) and decide whether it’s appropriate to change the link.
Q: How is data updated on this page?
Each time the user lands on one of your pages the script searches for GetYourGuide integrations. At this moment the data gets updated. Note that there can be delays in data.
Q: Why don’t the number of bookings on the integrations page match the number of bookings in the performance page?
For the integrations table we are using a last-click attribution model while the performance page shows you 31-days cookie attribution model (for which you get paid). Read more about this here
Q: Why are some of my integrations not showing up on the Integrations page?
For integrations to show up you must have Integrations Analyzer installed on all of your pages. Please, make sure that you have installed that correctly with this guide. If that doesn’t help, contact our Partner Support team to assist you here.
Q: Why does my integration’s status say “Broken”?
Broken link means that this link either:
- Is missing your cookie id (parameter: partner_id=)
- Is having a utm_force=0 parameter in the link
If you forget to insert the partner_id parameter into the link or accidentally insert utm_force=0 parameter then there is a high chance the bookings made through such links will not be attributed to you.
We suggest you immediately fix such links. Please use our link-builder tool to create new deeplinks. This way you can make sure that they’re working properly.
| Note: the utm_force=0 parameter breaks the attribution only if it was inserted in the link when you integrated it in your content, otherwise there is no risk. It is very common to see that parameter appear after clicking on a link, and this does not affect attribution. |
Q: Why does my integration’s status say “Active”?
Active means that the link is working fine and you are able to receive all the revenues from it
Q: Why does my integration’s status say “Inactive”?
Sometimes tours get deactivated. It can happen due to different reasons: from travel restrictions to attractions closing for a period of time etc.
For widgets: When the tour gets deactivated it will not show up in your widget anymore. Therefore, you should consider replacing the deactivated tour in your widget with an alternative tour.
Q: Why does my integration’s status say “Redirected”?
Sometimes tours get deactivated. It can happen due to different reasons: from travel restrictions to attractions closing for a period of time etc.
When the tour gets deactivated we redirect all the users coming via a link to that tour to a general POI page or a search page.
| Example: If the Eiffel Tower tour gets deactivated, we redirect users to a Paris page or an eiffel tower search page. |
We suggest you keep an eye on such links and fix them when it’s appropriate
Q: Do I have to change all links marked as “Broken”?
Yes. We are only able to attribute a booking to you (and credit your commission) if the link works properly. Please use our link-builder tool to make sure you have no errors.
Q: Why do I sometimes see links from Google Translate or other links nor related to my website?
Sometimes customers use Google Translate or other services to access the web pages. When the user goes to Google Translate and opens your website through it then the details of the page owner get hidden. That is why we display this as a Google Translate link as we are not able to identify the exact page the user is translating.