Mapp Intelligence: Page Request ID in the Raw Data Export

Prev Next

16 November 2026 You can now link products, orders and event data in the Raw Data Export directly to the page call on which they were measured. So far, this was not possible for data sent with event requests that do not appear in getFullClicks. For example, products from product list tracking could not be assigned to the page on which they were listed. The new, optional PAGE_REQUEST_ID column closes this gap. Existing exports stay unchanged.


Summary of changes

  • Direct join with the page call: PAGE_REQUEST_ID matches REQUEST_ID in getContents, so a single join links a row to its page. See Linking the Raw Data Tables.

  • New column in six tables: PAGE_REQUEST_ID is added as the last column to getFullBasket, getFullOrders, getFullCampaigns, getFullCustomerJourney, getFullCustParaProduct and getFullCustParaClick. See Contents of Raw Data Tables.

  • No change to existing columns: REQUEST_ID keeps its meaning and still identifies the request that measured the data.


Availability

The column is available for all Mapp Intelligence accounts that use the Raw Data Export. It is not active by default. To activate it for your account, contact the Mapp Support Team. With the upcoming Analytics settings in Mapp Cloud, you will be able to activate it yourself.

Warning

Activating the column adds one column at the end of each affected table. If your import or processing relies on a fixed number or order of columns, adjust it before the column is activated.

For an overview of the export, see Raw Data Export.