Reporting

The Reporting API enables retailers to programmatically retrieve advertising performance data for campaigns running through their retail media program.

Reporting is available at multiple levels, allowing your integration to analyze performance across advertisers, campaigns, and products.

Reporting Structure

The API provides reporting at four levels:

Advertiser Reporting

Advertiser reporting provides performance data at the advertiser level.

Use this report when your integration needs to understand or aggregate advertising performance by advertiser across your retail media program.

Common use cases include:

• Building advertiser-level performance dashboards

• Comparing performance across advertisers

• Supporting advertiser reporting and reconciliation workflows

• Aggregating performance for downstream analytics systems

Each result represents performance associated with an advertiser for the requested reporting period.

Campaign Reporting

Campaign reporting provides performance data at the campaign level.

Use this report when your integration needs to analyze the performance of individual campaigns created for advertisers within your retail media program.

Common use cases include:

• Displaying campaign performance in an external platform

• Comparing performance across campaigns

• Monitoring campaign delivery and outcomes

• Exporting campaign data to your reporting or analytics environment

Campaign identifiers can be used to associate reporting results with campaign records maintained by your own systems.

Product Reporting

The Reporting API provides two different product-level views: Promoted Products and Purchased Products.

The distinction between these reports is important when analyzing product-level advertising performance.

Promoted Products

Promoted Products reporting provides performance associated with products that were promoted through advertising.

Use this report to understand how the products included in advertising activity performed.

For example, this report can help your integration answer:

• Which products were promoted?

• How did advertising perform for each promoted product?

• Which promoted products generated the strongest results?

Purchased Products

Purchased Products reporting provides information about products purchased as a result of attributed advertising activity.

The purchased product does not necessarily need to be the same product that was originally promoted.

This report can therefore help your integration understand the broader commerce impact associated with advertising.

• Use Promoted Products when you want to analyze performance based on what was advertised.

• Use Purchased Products when you want to analyze what customers ultimately purchased.

Requesting a Report

Reporting requests use a defined reporting period and the applicable report endpoint.

1. Choose the Reporting Level

Select the report based on the level of data your integration needs:

• Advertiser

• Campaign

• Promoted Product

• Purchased Product

2. Define the Reporting Period

Specify the date range for which performance should be returned.

Use a consistent reporting period when comparing results across multiple reports or integrating Symbiosys reporting with another reporting system.

3. Apply Applicable Filters

Use the filtering options supported by the selected report to limit results to the resources relevant to your integration.

Refer to the API Reference for the filters supported by each reporting endpoint.

4. Process the Results

Reporting results can be stored, displayed, or combined with data in your retailer's own systems.

Working with Reporting IDs

Reporting results contain resource identifiers that allow your integration to associate performance with resources managed through the API.

Depending on the report, these can include identifiers for resources such as advertisers, campaigns, or products.

Your retailer may also maintain its own identifiers for resources managed through Symbiosys. Where supported, these identifiers can help reconcile API reporting with records in your own systems.

Pagination

Reporting results may contain more records than can be returned in a single response.

Use the pagination parameters supported by the applicable endpoint to retrieve the complete result set.

When ingesting reporting data programmatically, your integration should continue requesting pages until all available results for the requested reporting period have been retrieved.

Reporting Considerations

When integrating reporting data into your own systems, consider the following:

Reporting Level

Choose the report that corresponds to the entity your integration needs to analyze. Avoid assuming that metrics from one reporting level can be directly compared with another without considering the underlying grain.

Attribution

Conversion and sales metrics reflect the attribution methodology applicable to the advertising activity being reported.

When presenting attributed performance outside of Symbiosys, ensure that users understand the attribution context associated with the data.

Data Freshness

Advertising performance can continue to change after activity occurs as delivery and attributed outcomes are processed.

Consider this when determining how frequently your integration retrieves recent reporting periods.

Historical Data

If your integration maintains its own reporting history, determine whether recent reporting periods should be refreshed to capture changes to previously reported performance.

API Reference

For reporting endpoints, request parameters, response schemas, available metrics, filters, and supported values, see the API Reference.