Edge
The screens that control what your website and apps collect, and what they show visitors.
Edge is the part of Optima that faces the public internet. Your website and apps talk to it through the Optima SDKs: the SDK reports page views and events, asks it which content to show, runs consent banners and renders your forms. The screens in this section decide what Edge accepts and what it serves. Nothing arrives from a visitor's browser or phone unless you have allowed it here.
Edge screens sit in two places in the console. Tracking is in the Data group, because it is data coming in. Digital content and Forms are under On-site, because they are what a visitor sees when they come to you.
| Screen | Use it to | Package |
|---|---|---|
| Tracking | Choose which profile type anonymous visitors become, create SDK keys, map SDK events to your event types, run third-party tags and connect a consent platform. | Core |
| Digital content | Publish banners, personalised blocks, recommendations and the consent banner that your site and apps fetch. | Digital |
| Forms | Build sign-up and preference forms, hosted on their own page or embedded in your site. | Digital |
Smaller topics have their own pages:
- Tags: third-party scripts and pixels that run only after the visitor agrees.
- SDK keys and Identify signing: the public tokens your sites use, and how your backend proves who a logged-in visitor is.
- Consent banner and CMP and CMP mapping: asking visitors for consent, or reading the answer from your existing consent platform.
- Web personalization: showing different text to different visitors.
- Recommended items: product or content recommendations on your site.
Who uses it
App developers and integration specialists set up Tracking. Campaign creators write content and forms. Privacy officers review consent behaviour. Each page names the role it needs. Tracking and its tabs need integration_viewer to read and integration_editor to change. Digital content and Forms need content_viewer to read and content_editor to change. Or another role your administrator has given access to this area — see Licences and roles.
Typical order of setup
- In Tracking, choose the tracking entity and device identifier, and set the public base URL.
- Create an SDK key for your website or app, and install the SDK. The SDK guides are under SDKs.
- Add category mappings so page views and events become events in Optima.
- Decide how consent is collected: a consent banner from Optima, or your own consent platform through CMP mapping.
- Publish content and forms.