Google Tag Manager

Forum Discussion

DRamirez's avatar
DRamirez
Mentor
22 days ago

Landing pages data tracking

Hi everybody!

I was wondering, does anybody have any experience yet with the data side of landing pages? I am currently trying to implement a landing page in our NPS flow (so that, next to the score, we will also receive additional feedback from users), but I come across two things:

  • Does anybody know if there is already a currents integration established for the data that we are tracking through the landing pages?
  • When i incorporate the landing page url in an email, the link alias seems to disappear so we we wouldn't be able to track scores the way we used to anymore. Does anybody know the solution how we can use the landing page variable in a link while maintaining the link alias?

Curious to hear about everybody' experience!

Daniel

  • Divyesh's avatar
    Divyesh
    Collaborator

    I understand you’re facing two challenges with landing page data in your NPS flow:

    1. Currents Integration for Landing Page Data:
      Currently, landing page form submissions (along with associated tracking data) are automatically linked to a user's profile. This data is captured and can be reviewed via the Landing Page Details in the Braze dashboard under Messaging > Landing Pages. However, there isn’t an out‐of‐the‐box Currents integration specifically dedicated to landing page data. In other words, while you can track submissions and related metrics (like page views, clicks, conversions), this data isn’t automatically pushed through Currents. You could potentially integrate or export data using Braze’s API if you require Currents-like functionality, but there isn’t a pre-built Currents integration for landing pages at this time.
    2. Using the Landing Page URL Liquid Tag with a Link Alias:
      When you incorporate the {% landing_page_url your_custom_handle %} Liquid tag directly in an email, the dynamically generated URL overrides or omits your original link alias. This happens because the landing page URL is being rendered as a unique destination link that Braze generates for tracking landing page interactions. As a result, the standard alias you might have applied via the Link tool or alias field isn’t preserved.

    Suggested Approaches:
    • For the Currents integration: Rely on the built‐in Landing Page analytics within Braze for aggregate metrics. If you need to push this data elsewhere, consider using Braze’s API or exploring a custom integration solution to extract landing page event data.

    • For preserving link alias functionality: Consider these options:
      - Embed the landing page URL within a manually crafted hyperlink. For example, create an anchor tag where the href is set to the rendered landing page URL (using the Liquid tag) while you display your preferred alias text. Note, however, that while the click may display your alias text, the underlying tracking URL might still not fully leverage Braze’s link alias system as expected.
      - Alternatively, if you rely heavily on link alias tracking for metrics (like tracking NPS scores), you might need to adjust your strategy by either incorporating additional URL parameters or using Braze’s link tracking tools in a way that complements landing page analytics.

    For more detailed guidance, please refer to the official documentation on landing pages and their tracking:
    • Learn about Tracking Users through a Landing Page: https://www.braze.com/docs/user_guide/message_building_by_channel/landing_pages/
    • And see information on landing page tracking data: https://www.braze.com/docs/user_guide/message_building_by_channel/landing_pages/#about-landing-page-tracking-data

    I hope this helps clarify the current behavior and potential workarounds.