Skip to content
English
  • There are no suggestions because the search field is empty.

🔍 Tracking Where Customers Clicked From To Reach Your Slerp Ordering Site

You can use your own analytics tools (such as Google Analytics 4 or Google Tag Manager) to understand where customers clicked from before landing on your Slerp online ordering site (e.g. yourbrand.slerp.com).

What you can (and can’t) see in Slerp Controls

Slerp Controls shows order and revenue performance, but it does not show the original click source (e.g. Google, Instagram, email, your main website) for each customer session. 

To see where customers clicked from to reach your Slerp ordering site, you need to use an external analytics tool such as Google Analytics 4 (GA4), connected via your Google Analytics ID or Google Tag Manager (GTM).

Once connected, all standard GA4 dimensions (e.g. source, medium, campaign, session source) can be used to analyse Slerp traffic and conversions.

Step 1 – Connect Google Analytics / Tag Manager to Slerp

For detailed guide on linking your SlerpSpace to GA4/GTM and others, see:

〽️ Marketing and Analytics

From this point onwards, page views and events from your Slerp ordering site will start flowing into your GA4 property. 

📝 Note:

There is no backfill for historical data — only data collected after connecting will be available.

Step 2 – Confirm data is being collected in GA4

After adding your IDs in Slerp Controls:

  1. Open your Google Analytics 4 property.
  2. Go to Admin → Data Streams, and select the relevant Web data stream.
  3. Check that the Measurement ID matches the one you entered in Slerp.
  4. Go to Reports → Realtime and confirm you see active users when you or your team visit your Slerp ordering site.

If you can see active users and page views for your Slerp domain (e.g. yourbrand.slerp.com), your tracking is working.

💡Tip:

GA4 Realtime data can take up to a minute or two to appear. If you don’t see data immediately, wait a moment before assuming there’s an issue.

Step 3 – See where customers clicked from (traffic sources)

In GA4, you can use standard reports to understand where users came from before landing on your Slerp ordering site.

A. High-level traffic sources

  1. In GA4, go to Reports → Life cycle → Acquisition → User acquisition.

  2. Use dimensions such as:

    • User source / medium (e.g. google / organic, instagram.com / referral, email / newsletter)

    • First user campaign (if you are using UTM tracking)

  3. To narrow down to Slerp traffic, add a filter using Hostname set to your Slerp domain (e.g. yourbrand.slerp.com).

This shows, at a high level, which channels and sources are sending users into Slerp.

B. Session-level traffic and landing pages

  1. Go to Reports → Life cycle → Acquisition → Traffic acquisition.
  2. Use dimensions such as:
    • Session source / medium
    • Session campaign
  3. Add a Secondary dimension like Landing page + query string to see which Slerp page users landed on from each source.

This helps you answer questions such as:

  • Are customers landing on Slerp from our main website or from social media?
  • Which campaigns drive the most traffic directly to specific menus or locations?

Step 4 – Tie traffic sources to orders and revenue

To see which traffic sources lead to actual orders, you’ll need ecommerce or conversion events configured in GA4. This is a more advanced setup that typically requires input from your developer, marketing agency, or analytics team.

⚠️ Important:

Adding your GA4 ID to Slerp Controls enables page view and session tracking automatically, but purchase and order events do not fire automatically. These require additional custom configuration.

There are two common approaches:

Ecommerce events via GTM / custom setup

Your developer or marketing team sends purchase events (e.g. purchase, begin_checkout) from Slerp into GA4 via Google Tag Manager.

Custom conversion events

You define a GA4 event that represents a completed order (e.g. a thank-you page view or a specific event name) and mark it as a conversion in GA4.

Once conversions are tracked, you can:

  • Use Reports → Life cycle → Acquisition → Traffic acquisition and add Conversions and Total revenue metrics to see which sources and mediums drive orders.
  • Build Explorations in GA4 to break down source / medium, campaign, landing page, conversions, and revenue in a single custom view.

✅ Best practices for tracking Slerp traffic sources

  • Use consistent UTM parameters on all links pointing to Slerp — from your main website, social media profiles, email campaigns, and paid ads.For example: utm_source=website&utm_medium=button&utm_campaign=online_order
  • Check that all your “Order Now” buttons (website, Instagram bio link, Google Business profile, etc.) point to the correct Slerp URL (your SlerpSpace domain or branded domain).
  • Regularly review GA4 Acquisition reports to see which channels drive the most sessions to Slerp, orders, and revenue.

FAQs

Can I see the click source directly inside Slerp Controls?

No. Slerp Controls does not currently expose the original marketing source/medium for each order. For that level of detail, you should use Google Analytics or another analytics platform connected to your Slerp site.

Does this work with a custom/branded domain instead of yourbrand.slerp.com?

Yes. As long as the GA4 or GTM ID is connected via the Marketing and Analytics settings, traffic to your Slerp-branded domain will still be tracked.

Can Slerp support configure GA4 or interpret my GA reports for me?

Slerp can help you confirm where to add your IDs in Controls and verify that tracking appears to be working. However, the detailed setup of GA4, GTM, ecommerce events, and campaign strategy is typically owned by your internal marketing/analytics team or agency.

Why don’t I see purchase or order data in GA4 automatically?

Adding your GA4 ID to Slerp Controls enables standard page view and session tracking, but ecommerce events (such as completed purchases) require additional configuration. This is not set up automatically and will need to be implemented by your developer or analytics team via Google Tag Manager or a custom integration.