Skip to content
Go to raptorservices.com
  • There are no suggestions because the search field is empty.

Tracking Template Adaptation

Extending Tracking for CDP Use Cases

Raptor provides a standard tracking template that supports Website Recommendations, Email Recommendations, Triggers, and Site Search.

When customers use Raptor CDP, tracking can be extended and configured to reflect the customer’s specific business, data model, and audience needs — without disrupting existing recommendation setups.

This article explains:

  • how tracking can be extended for CDP use cases
  • how this works when CDP is added after Recommendations
  • how to use Edit Parameters in practice
  • how the Control Panel, Data Manager, and Audience Builder work together

This article is part conceptual and part practical.
It focuses on how to work with the tracking template, not how to implement tracking code.

Tracking as a Shared Foundation

The same tracking foundation is used across Raptor products.

For customers using Recommendations:

  • the standard tracking template provides a stable base

For customers using CDP:

  • the same template is extended, not replaced


How CDP Extends Tracking (High Level)

When CDP is in scope, tracking is typically extended by:

  • adding new event types (non‑product or business‑specific)
  • adding additional parameters to capture richer context
  • structuring and interpreting data in the Data Manager
  • using the Audience Builder to define segments and logic

The tracking template stays recognizable and consistent — flexibility comes from configuration.

 

Using “Edit Parameters” (Practical Guide)

The Edit Parameters feature is the primary, supported way to adapt tracking for CDP use cases.

It allows you to control what data is sent, without changing the underlying meaning of the standard template.

Where to find it

Control Panel → Data Management → Implementing Tracking
→ Tracking Events → Edit Parameters

Each tracking event (Visit, Basket, Buy, custom events, etc.) has its own Edit Parameters option.

What “Edit Parameters” lets you do

Using Edit Parameters, you can:

  • include or exclude standard parameters per event
  • see exactly which parameters are part of the generated script
  • simplify payloads for CDP‑only or non‑product events
  • align tracking with the data you intend to model in CDP

Any changes are reflected immediately in the generated tracking script.

Typical CDP use cases for Edit Parameters

Examples where Edit Parameters is commonly used:

  • non‑product events that don’t need ProductId
  • content or interaction events that require different attributes
  • excluding unused parameters from custom events
  • auditing which parameters are actually sent in a customer setup

This is especially useful when CDP is introduced after Recommendations and new event types are added.

What Edit Parameters is not used for

Edit Parameters is not intended to:

  • redefine the meaning of standard parameters
  • replace ProductId with another identifier in Recommendation events
  • alter how recommendation modules interpret tracking
  • “re‑wire” the standard event model

Instead, think of 'Edit Parameters' as fine‑tuning what is sent, not redefining how Raptor uses tracking data.

Creating custom parameters (advanced)

If a required attribute is not part of the standard parameter list, you can use Create Parameter.

This is typically done for:

  • CDP‑specific attributes
  • custom business events
  • metadata that will be modeled in the Data Manager

Custom parameters should:

  • have a clear, stable meaning
  • not overlap with existing standard parameters
  • be documented as part of the CDP setup

In most cases, the standard parameters are sufficient, and custom parameters are used sparingly.

⚠️About Create Parameter access: At the moment, the Create Parameter option is available only to Raptor administrators. This means that:

  • Customers and partners can configure and use existing parameters via Edit Parameters
  • Creation of new custom parameters is currently handled by Raptor as part of CDP onboarding or project work
If your CDP setup requires additional parameters that are not part of the standard template, this can be coordinated with Raptor when designing the CDP data model.

Reviewing all parameters

A complete review of standard events and parameters are part of the tracking setup directly in the Control Panel regardless of whether you are working with client‑side tracking, server‑side tracking, or Google Tag Manager.

    Where to find it

    Control Panel → Data Management → Implementing Tracking

    For each tracking type, you can see:

    • the list of standard tracking events (e.g. Visit, Basket, Buy, etc.)
    • the parameters included for each event
    • parameter names, descriptions, data types, and whether they are required
    • how the setup differs depending on the selected tracking method

    This view reflects the active tracking configuration for the selected implementation type.

     

    Combining Recommendations and CDP

    Raptor Recommendations and Raptor CDP are built on the same tracking foundation.

    Whether they are introduced independently or together, the underlying tracking setup remains consistent:

    • standard recommendation events continue to work as expected
    • CDP functionality is added through extension and configuration
    • data is structured and interpreted via the Data Manager and Audience Builder

    This makes it possible to use Recommendations and CDP side‑by‑side and expand functionality over time without changing existing tracking implementations.

     

    Where Data Modeling Actually Happens

    While tracking defines what is sent, CDP logic is defined elsewhere:

    • Data Manager

      • defines entities, relationships, and attributes
      • normalizes incoming tracking data

    • Audience Builder

      • uses the structured data to build segments
      • applies logic across events, attributes, and time

    This separation ensures:

    • tracking remains stable
    • CDP remains flexible
    • data remains consistent over time

     

    Summary

    • The standard tracking template provides a stable base
    • CDP extends tracking through configuration, not replacement
    • Edit Parameters is the practical tool for shaping CDP payloads
    • Data Manager and Audience Builder define how data is structured and used
    • Recommendations and CDP are designed to work together
    • Extending tracking for CDP does not break existing recommendation setups

    When working with CDP, think in terms of extension and modeling, not alteration.