Rokt Documentation
  • Documentation
  • User Guide
  • SDK
  • API
  • Third-Party Integrations
  • Help

›Integration Examples

Getting Started

  • Introduction

Web SDK

  • Overview
  • Architecture
  • Integrating the Web SDK
  • Integration Examples

    • Confirmation Page Integration
    • Preparative Iframe
    • Page Identifier
    • Single Page Applications
    • Brand Conversion Integration
    • In Transaction/Cart Integration
    • Event-based Integration
    • Sandbox Integration
  • Integration Best Practices
  • Attributes
  • Security
  • Mobile In-App Web Pages
  • API

    • README
    • Globals

    Enumerations

    • FailureReason

    Interfaces

    • Attributes
    • Cart
    • CartItem
    • PlacementCloseEvent
    • Rokt
    • RoktConfiguration
    • Widget

iOS SDK

  • Overview
  • Version
  • Integrating the SDK

    • Integrating and Initializing the SDK
    • Launching an Overlay Placement
    • Launching an Embedded Placement
    • Recording a Brand Conversion
    • Sandbox Integration
  • Attributes
  • Security

Android SDK

  • Overview
  • Version
  • Integrating the SDK

    • Integrating and Initializing the SDK
    • Launching an Overlay Placement
    • Launching an Embedded Placement
    • Recording a Brand Conversion
    • Sandbox Integration

    Attributes

    • Core Attributes
    • Vertical Attributes
  • Security

React Native SDK

  • Overview
  • Version
  • Integrating the SDK

    • Integrating and Initializing the SDK
    • Launching an Overlay Placement
    • Launching an Embedded Placement
    • Recording a Brand Conversion
    • Sandbox Integration

    Attributes

    • Core Attributes
    • Vertical Attributes
  • Security
Edit

Page Identifier

This scenario is an addition to other integration examples and explains how to pass a page identifier in the Web SDK. A page identifier is a unique name for the page where you are planning on displaying Rokt placements. This provides the opportunity to identify the page uniquely (e.g., 'checkout-offers-step').

Note: when page identifier is passed, the page URL will be ignored for detection purposes.

This is useful in the cases where there is a multi-step checkout flow that may have the same URL on various pages, when you want more control over what step or page someone is on within your checkout flow, or to set up different layouts of the same page, based on customer journeys.

The integration follows the same steps as in previous examples, but adds an additional pageIdentifer parameter to be passed to the initialisation function.

See Rokt.init for more details on the method.

rokt.onLoaded(function(rokt) {
    rokt.init({
        pageIdentifier: '',
    });
    // Integration steps as per other examples
});
← Preparative IframeSingle Page Applications →
RESOURCES
DocumentationUser GuideSDKAPIIntegration PartnersHelp
COMPANY
About UsContact UsCareersEngineering Blog
Rokt Documentation
Copyright © Rokt 2021 - All Rights Reserved