Adobe Analytics Destination

Forward events from Ours Privacy into your existing Adobe Analytics report suite — pageviews, custom events, eVars, props, and commerce — without exposing patient or customer data to your browser-side measurement code.

Open Destinations in app

---

Why use this destination

• Keep your existing Adobe reports working. Events land in the same report suite your team already analyzes, so pages, eVars, props, and commerce reports keep functioning the way they do today.
• Run alongside the AppMeasurement library. Server-side hits can be stitched with browser-side hits when you forward the Experience Cloud ID, so cross-channel analysis still works.
• Fan out to multiple report suites. Write the same event into more than one report suite by listing the IDs together — useful for production / rollup splits.
• Privacy controls on every field. Redact, hash, or suppress sensitive fields with Ours Privacy's standard PII controls before events reach Adobe.

---

How to configure

1. In Adobe Analytics, open Admin → Report Suites → [your suite] → Edit Settings → General → Server and copy the tracking server hostname (do not include https:// or any path). If you already run the AppMeasurement library, this is the same value as s.trackingServer.
2. From the same Admin area, copy the Report Suite ID for the suite you want events written to. The friendly name and the ID are different — copy the ID.
3. (Optional) In Admin → Experience Cloud → Organization, copy the Marketing Cloud Organization ID if you also run an AppMeasurement implementation client-side and want server-side and client-side hits stitched as the same visitor.
4. Open Destinations in Ours Privacy, click Add destination, choose Adobe Analytics, paste the values above, and press Save.
5. Configure your event mappings in the destination's mapping UI. The tooltips on each field describe where the value comes from and how Adobe interprets it.

To write the same event into multiple report suites at once, paste the IDs together as rsid-prod,rsid-rollup in the Report Suite ID field.

---

Privacy and compliance

This destination runs through Ours Privacy's standard event pipeline, so PHI fields can be redacted, hashed, or suppressed before they ever reach Adobe. You control which events are forwarded through your Allow List, and the visitor IP is forwarded to Adobe in a way that lets Adobe perform GeoIP enrichment on the visitor — and can be modified or removed entirely using Ours Privacy's standard IP controls.

---

Troubleshooting

• Events arrive in the wrong report suite. Confirm the Report Suite ID in Ours Privacy matches the ID in Adobe character-for-character. Adobe accepts the hit and silently drops it when the ID is wrong.
• Events are missing from Adobe entirely. Open Live Stream inside your Adobe report suite — if events show there but not in standard reports, you are looking at standard-report lag (typically 30–90 minutes), not a delivery problem. If they are not in Live Stream either, double-check the Tracking Server value.
• All visitors appear as a single visitor. Set the Visitor ID mapping in the destination so each visitor is identified consistently across hits.
• Geo reports look wrong or collapsed. Confirm the IP mapping is set on the destination so the visitor's IP — not a server IP — is what Adobe sees.

---

Next Steps

• Destinations Overview — see all available destinations and how routing works.
• Visitor Properties Overview — how visitor identity flows through the pipeline.
• Allow List — control which events are forwarded to which destinations.

If you have questions, reach out to support@oursprivacy.com.