Skip to main content
Fospha is a marketing measurement platform. It takes your ad-platform spend plus its own site and conversion signal, re-attributes conversions and revenue across channels, and exposes the result through its Export API. SourceMedium syncs that output so Fospha’s re-attributed view sits beside the numbers each ad platform reports for itself.
Fospha is a measurement source, not an ad platform. It does not replace your Meta, Google, or TikTok connectors. Every row lands with the Fospha attribution next to the ad platform’s own figure and a last-click baseline.

​
What you need

Fospha issues these to you. Ask your Fospha account manager, Customer Success Manager, or Fospha Support for all of them in one thread, then paste them in SourceMedium. Do not email the values.
Fospha requires three values, not two. Fospha uses the word “client” for two unrelated things. The application credentials alone will mint a valid token and still fail every query.
The first two mint an access token. The third tells Fospha whose data to return, and Fospha issues it separately from the credential pair. Fospha’s own documentation lists it as a distinct prerequisite:
“Before you begin, ensure you have: the Fospha client ID for your brand; a valid access token. If you do not have the Fospha client ID yet, please contact Fospha support.” Fospha, Retrieve data
You also need to confirm two settings, because neither can be discovered reliably and both change the numbers:
  • Your Fospha region, US or UK. These are separate deployments, and credentials only work against the right one.
  • Your reporting currency. SourceMedium asks Fospha for USD unless told otherwise (Fospha’s API returns EUR when no currency is specified). If your Fospha account reports in another currency, open a support ticket after you connect so we set it before the first sync.

​
How to connect

Paste the three Fospha values and your region in SourceMedium. Do not email them.
You connect data sources yourself in SourceMedium. Sign in to your SourceMedium account, open your store, then in the Data sources section click Connect data source and choose the platform. You need an Editor or Admin role on the store. If you have view-only access, ask an admin or editor on your team to connect it.Once it is connected, what happens next covers first-sync timing and what each connection status means.
1

Request all three values from Fospha

Ask your Fospha account manager, CSM, or Fospha Support for the app_client_id, the app_client_secret, and the Fospha client ID for your brand. Name the third one explicitly. The credential pair is often sent on its own, so “we have the client ID and secret” is a common but incomplete answer.While you are in that thread, also ask which region your account uses (US or UK) and how far back Fospha restates attributed conversions and revenue.
2

Add the values in SourceMedium

Find Fospha in the connector picker and click Connect. Enter:
  • Credentials: app_client_id:app_client_secret:brand_client_id as one value
  • Region: us or uk
Click Connect. SourceMedium checks that the credentials work before saving them.
3

Confirm it is connected

The connection reads Awaiting first data until the first sync lands, then Connected.
SourceMedium only ever reads from your connected platforms. It does not create, change, or delete anything, so create the key with read-only access wherever the platform offers it. Treat it like a password: keep it confidential and avoid sharing it over email or in spreadsheets. If the credential is rotated or revoked, follow this guide’s connection method to update SourceMedium.

​
What data syncs

Every row records the currency it is denominated in, so a figure can always be traced back to its unit. Where it lands in the warehouse: rpt_media_mix_channel_daily for channel-level comparison, and obt_media_mix_performance for campaign and ad detail.

​
Reading the data correctly

Recent days are incomplete, by design. A Fospha date is not settled the next day, even after Fospha’s own daily pipeline reports complete. Measured on a live account, the previous day held about a third of its eventual spend, while every older day sat within a few percent of normal. Treat roughly the last three to four days as still filling in, and compare on settled windows.
  • Fospha restates history. As conversions move between channels, a past date’s rows change, and some disappear entirely. SourceMedium rewrites the affected window on each sync, so what you see always matches Fospha’s current view.
  • Fospha attribution will not match platform-reported numbers, and that is the point. Re-attribution moves credit between channels. Use the platform-reported and last-click columns that land alongside it when you need the comparison.
  • Fospha covers marketing measurement only. Order, customer, and catalog data come from your commerce platform integration.

​
Troubleshooting

  • “Access denied: invalid client credentials”? This almost always means the Fospha client ID for your brand is wrong or missing, not that the credential pair is bad. Fospha returns the same message for both. If a token was issued at all, the application credentials are fine. Check the brand client ID before asking anyone to rotate a secret.
  • Authentication fails outright? Confirm which region your Fospha account is on. The wrong region rejects a good credential in a way that looks identical to a bad one.
  • Numbers look plausible but wrong, roughly by an exchange rate? Confirm your reporting currency with SourceMedium. Fospha returns EUR when no currency is specified, which produces well-formed but incorrect figures with no error anywhere.
  • A recent day looks low? See the note above on settling. Check whether the date is inside the last few days before treating it as a real drop.