extensions/amp-consent/cmps/ogury.md
amp-consent component JSON configuration<amp-consent id="ogury" layout="nodisplay" type="Ogury">
<script type="application/json">
{
"postPromptUI": "custom-prompt-ui",
"clientConfig": {"assetKey": "OGY-316B32F7E5B7"},
"uiConfig": {"overlay": true}
}
</script>
<div id="custom-prompt-ui">
Post Prompt UI
<button on="tap:ogury.prompt(consent=Ogury)">
Privacy Settings
</button>
</div>
</amp-consent>
postPromptUIThe value of postPromptUI should be the id of the html tag in which the consent ui will be attached to. In our example above, the value of postPromptUI is custom-prompt-ui since we have a div with that id.
Notice in the example above, we have a button with the attribute on="tap.ogury.prompt(consent=Ogury)". The id of your <amp-consent> element is relevant here. Notice how the id of our <amp-consent> is consent, that's why the on attribute has the value "tap.consent.prompt(consent=Ogury)"
clientConfig)| Attribute | Type | Mandatory | Description |
|---|---|---|---|
| assetKey | String | yes | Your asset key can be found in your publisher dashboard. |
For more information on how to integrate AMP to your page please visit our integration documentation in your publisher dashboard or contact your account manager directly.