Vue SDK
Placement with no dashboard id — location
Instead of a numeric id created in a dashboard, <EzoicAd location="...">
places an ad by its semantic name. The component resolves the name to a reserved placeholder id
for you.
What this demonstrates
Once the ad bundle has loaded, the SDK resolves the name through
GetGeneratedIdAsync(location); before the bundle is available it resolves against
its own copy of Ezoic's reserved location map, so the placeholder still appears on first paint.
location placements default required: true (that is what marks a
900-range id as zero-config server-side) and must pass sizes —
there is no dashboard sizing to fall back on, so the SDK warns loudly in dev when it is omitted.
Two <EzoicAd location="..."> with the same name resolve to distinct ids
rather than colliding.This is separate from Ezoic's newer id-less
showAds({anchor, ...}) descriptor (a raw JS call with no component wrapper, used on
the Id-less showAds pages) — the SDK resolves location
through GetGeneratedIdAsync and its own reserved-location map rather than the
anchor-element descriptor.SDK docs: README — Zero-config placements (location)
Component usage
<script setup lang="ts">
import { EzoicAd } from '@ezoic/vue-sdk';
</script>
<template>
<EzoicAd location="top_of_page" :sizes="['728x90', '320x50']" />
<EzoicAd location="under_first_paragraph" :sizes="['300x250']" />
</template>Live demo
The panel below embeds the SDK's own demo app (built from
@ezoic/vue-sdk v1.0.0) — look at its "Display ads — zero-config
locations" panel for this scenario. examples.ezoic.com's root domain is
not lite-active, so the ad request will not fill here — check the placeholder div and ids, not
the fill. Open the full demo in a new tab →