How to Use Integration Reporting

Wunderkind Integrations deliver real‑time behavioral triggers into client email and/or SMS platforms, enabling brands to drive performance and extend reach without disrupting existing workflows; brands retain control over creative, cadence, and delivery while Wunderkind powers the intelligence and decisioning behind the scenes.

Integrations Reporting is live for AMP clients, providing a consistent, transparent way to measure Integrations activity across identification rates, events, and sends; Phase 1 focuses on Sends Metrics and visibility into IDs, events, and sends, and Phase 2 will introduce revenue attribution metrics connected to client ESPs and interactive dashboards and funnels for deeper performance insights.

Table of Contents

1. How to Access Integrations Reporting

2. What Appears in the Report

3. How Integrations Reporting Parses and Categorizes Data

4. Example Workflows Integrations Reporting Enables

5. Troubleshooting and FAQs

How to access Integrations Reporting

1) Log into the Wunderkind Platform at https://platform.wunderkind.co/ using standard credentials.

2) Select “Analytics” and “Reports” in the left navigation and open the “Integrations Standard Report” to view sends‑level Actions metrics alongside identity and event health indicators.

Tip: If the report does not appear, the account may not yet have the Integrations reporting flag enabled; the Wunderkind team can verify availability at the website level.

What appears in the report: metrics and definitions

Integrations Reports helps clients understand how Integrations increases reach and activation volume across email and text by standardizing a core set of health metrics in one place.

Cross‑channel (email + text) health metrics available in Platform include:

Wunderkind Data

• Total Actions: Count of behavior‑based actions (data‑only) sent to the ESP/SMS.
• Action Rate (Actions per Visit): Total Actions divided by total visits, indicating activation intensity relative to traffic volume.
• Total ID (Onsite Identified): Total identified pre‑conversion visits, used as a baseline for audience reach.
• Onsite ID Rate: Total identified pre‑conversion visits divided by total visits.
• Actions ID Abandonment Rate: Eligible identified visits divided by total visits, aligned to the identification portion of the abandonment funnel.

ESP Data

*Data currently available for Klaviyo and Braze. Salesforce, Bloomreach, and more ESP data coming soon.

• Sends: Total email or text sends sent by the ESP after receiving the Wunderkind Action event
• Opens: Volume of emails that were opened as measured by the ESP
• Clicks: Volume of emails or texts that were clicked as measured by the ESP
• Conversions: Total conversions attributed to Actions clicks as measured by the ESP
• Revenue: Total revenue attributed to Actions clicks as measured by the ESP

Note: WKND-attributed revenue shown here may not yet reflect a complete picture of your performance. For now, please use your analytics platform (GA4/Adobe) or ESP-attributed data as the most reliable source. If you’re on Klaviyo, Klaviyo-attributed data is available in Platform.

• Sends to Visit Rate: Total sends as measured by the ESP divided by total visits
• Sends to Action Rate: Total sends as measured by the ESP divided by the total Actions sent

The Integrations Reach Standard Report in Analytics covers Total Actions, Onsite total ID, Action rate, Onsite ID rate, and Actions ID abandonment rate. Additional metrics can be added to the Standard Report and saved as applicable. 

How Integrations Reporting Parses and Categorizes Data

For reporting to work accurately, your flows, canvases, or campaigns need to follow Wunderkind's standardized naming conventions. We use these names to automatically identify key details like module, purpose, and part number. If names don't follow these conventions, some data may be missing or miscategorized in your reports.

Wunderkind Attribution

Klaviyo & Braze: To ensure your flows and canvases are recognized as Wunderkind-managed, include the tag wknd on each one. Any flow or canvas tagged with non-wknd will be excluded from Wunderkind reporting.

Bloomreach: Wunderkind campaigns in Bloomreach are identified automatically using your Wunderkind campaign ID — no additional tagging is required.

Part

The flow message name (Klaviyo) / step name (Braze) / action name (Bloomreach) is used to identify the message part. We can automatically recognize a part number when the name follows one of these formats:

• "Part" followed by a number — e.g., Abandonment Part 1
• "Email" or "SMS" followed by a number — e.g., WKND Low Stock Email 1
• A "#" followed by a number — e.g., Back in Stock #2
• A fraction-style format — e.g., abandonment_1_of_2 or pricedrop_1of2

When a message name matches one of these patterns, we'll correctly assign it a part number for reporting.

If the name doesn't follow one of these formats, the message will appear as "Unspecified" in reporting. For example, names like wk-browse-abandonment-1, Customers $10 Off, or Catalog 3 of 4 won't be recognized because the number either appears in a different context or follows an unsupported pattern.

Module

The flow name (Klaviyo) / canvas name (Braze) / campaign name (Bloomreach) is used to identify the campaign module. We automatically detect keywords in the name to categorize it. The following keywords are recognized:

• Names containing atc, cart, basket, category, catrecap, browse, product, prod, or aban → Abandonment
• Names containing welcome → Welcome
• Names containing price drop, back in stock, or low stock (variations like "pricedrop," "backinstock," or hyphenated formats are also recognized) → Catalog
• Names that don't match any of the above → Other

Purpose

The flow name (Klaviyo) / canvas name (Braze) / campaign name (Bloomreach) is also used to identify the campaign purpose. We automatically detect keywords in the name to categorize it. The following keywords are recognized:

• Names containing atc, cart, or basket → Cart
• Names containing category or catrecap → Category
• Names containing product, prod, or browse → Product
• Names containing welcome → Welcome
• Names containing back in stock (variations like "backinstock" or "back-in-stock" are also recognized) → Back in Stock
• Names containing price drop (variations like "pricedrop" or "price-drop" are also recognized) → Price Drop
• Names containing low stock (variations like "lowstock" or "low-stock" are also recognized) → Low Stock
• Names containing aban → Other Abandonment
• Names that don't match any of the above → Other

For AI campaigns: To ensure AI-driven campaigns are correctly identified in reporting, the flow, canvas, or campaign name must include the word "AI" (capitalized). For example:

• "AI - Cart Abandonment"
• "AI - Price Drop"

Competitors

To support competitive performance analysis, we automatically identify flows, canvases, or campaigns belonging to other vendors based on keywords in the name. Any flow not identified as Wunderkind-managed will be scanned for the following vendor keywords:

• Names containing elevar → Elevar
• Names containing shopify → Shopify
• Names containing reclaim or retention → Reclaim
• Names containing opensend → Opensend
• Names containing sonar → Sonar
• Names containing native → Native
• Names containing r.ai → R.ai
• Names that don't match any of the above → ESP

Example workflows Integrations Reporting enables

• Identify whether onsite recognition and triggered sends are scaling by tracking Total ID, Total Actions, and Action Rate over time.
• Assess activation health relative to traffic by monitoring Actions per Visit and Onsite ID Rate across time windows or segments.
• Prioritize optimization by using ID and Integrations health trends to plan new flows and event mappings ahead based on performance metrics.

Troubleshooting and FAQs

• The Integrations report does not appear in Analytics. What should clients do?
  Integrations Reporting appears when Actions data is present and flagged for the website(s). If the report is not visible, your Wunderkind team can confirm that the Integrations reporting flag/eligibility has been enabled.
• Why are opens/clicks/revenue not visible for my ESP yet?
  Engagement and revenue data is available for Klaviyo only at this time. Phase 1 of Integrations Reporting focuses on standardized Sends and identity/event health; ESP feedback‑loop metrics (e.g., delivered, opens, clicks, conversions, revenue) will be launched for each ESP as these integrations are completed. Separately, WKND-attributed revenue in Analytics may not yet reflect a complete picture — GA4/Adobe or your ESP-attributed data (available now for Klaviyo) is the most reliable source today while we continue to improve reporting with full event-level data ingestion.