Skip to main content

Prism

Recommended for most custom-UI builds.

Prism is AdGem's Offer Personalization API — a GraphQL API for building your own offer experience. You own the UI; Prism supplies the offers, already personalized.

Why Prism​

Prism returns offers that are sorted, suppressed, and geo- and device-filtered for the player you request them for. You get our personalization as an input to your own UI, so you don't have to build a ranking engine to launch a strong experience.

Because you own the UI, you keep final control over how offers are presented — you can display or re-order them however you like. The personalization is additive, not a takeover.

When to choose it​

  • You want a custom offer UI and AdGem's personalization.
  • You want to keep control of presentation without building ranking logic from scratch.
  • You're on any platform — Prism works wherever you can make API calls.

If you'd rather build your own ranking on the raw catalog, see the Offer API. If you'd rather not build a UI at all, see Pre-built.

Attribution​

Each offer's click_url is returned ready to fire. Because you own the click, you're responsible for decorating it with the device advertising ID so installs can be attributed deterministically.

Read the advertising ID in your app — IDFA on iOS (after obtaining App Tracking Transparency consent) or GAID on Android — and append it to the click_url before opening it.

On iOS:

<click_url>&idfa=<IDFA>

On Android:

<click_url>&gaid=<GAID>

AdGem passes the ID to the advertiser's measurement partner (Adjust, AppsFlyer, etc.) on the click, provided the advertiser's tracking template includes the corresponding macro. The measurement partner then matches the install to the click by device ID. When the user has allowed tracking in both your app and the advertised app, this is the most reliable attribution there is; without it, matching falls back to fingerprint matching and, on iOS, SKAdNetwork — far less reliable.

note

The advertising ID can only be read by native app code — a browser or WebView cannot supply it. Read it natively and append it to the click_url before firing the click.

Build with Prism​

See the Prism reference for the endpoint, authentication, queries, and examples.