Ad Embed Placements
Connect a third-party ad provider, define placement zones, and embed ad iframes on pages and blog posts on ArtInStack.
Ad embed is third-party advertising inventory—separate from affiliate recommendation cards and from fundraising campaigns under Settings → Campaigns (see Donations and fundraising campaigns). Configure your network under Settings → Integrations → Ad embed, create placements by zone (header, in-content, sidebar), then add Ad embed blocks in the page editor or blog. Ads load through a wrapper on your site. Render counts (not ad-network revenue) appear under Analytics → Ad embed when ads are enabled on your plan—see Dashboard analytics overview.
Prerequisites
Dashboard → Settings → Integrations → Ad embed
Eligible plan with ads capability
Supported ad providers
Pick Provider under Settings → Integrations → Ad embed. One provider applies site-wide; each placement row supplies the slot or unit id your network gave you.
| Provider in dashboard | Best for | Live ads on your public site |
|---|---|---|
| Google AdSense | Most independent sites and blogs starting ad monetization | Yes — recommended default; full first-party embed on your domain |
| Mediavine | Sites already approved on Mediavine | Yes — requires Mediavine site id + placement/slot on each placement row |
| Carbon | Newsletter / creative-community style Carbon contracts | Yes — requires Carbon serve + placement ids per row |
| Other (advanced) | Experiments only | No — reserved shell for future providers; not for earning ad revenue today |
Local preview on localhost may show a labeled placeholder instead of a live creative; use your live custom domain (AdSense-approved) to verify real delivery.
Recommended for photo and creative sites
- Google AdSense is the best first choice on ArtInStack: one publisher id, standard IAB sizes (rectangle, leaderboard, skyscraper) in Add placement, and render analytics in Analytics → Ad embed.
- Choose Mediavine or Carbon only if you already have an active contract with that network—enter the same ids you use in their dashboard into Publisher / site id and each placement’s slot fields.
- Avoid Other (advanced) on production pages until ArtInStack documents a supported provider there.
Keep ad zones sparse on portfolio and gallery pages—one in-content placement plus an optional header slot usually balances revenue and UX better than stacking multiple units.
How it works
Integrations → Ad embed: provider (for example AdSense), publisher or client id, and one or more placements—each with a name, zone (header, in-content, sidebar), and size/format you choose.
Page editor / blog: Ad embed block selects a placement you already saved—you do not paste ad script tags into the editor.
On the live site: visitors see the ad slot through your site’s embed wrapper when the network allows delivery.
Implementation steps
- Open Settings → Integrations → Ad embed and connect the provider fields your network issued.
- Create at least one placement with a clear zone name you will recognize in analytics.
- In Pages → Edit (or a blog post), add an Ad embed block and select that placement.
- Publish only on pages that satisfy the network’s content and density rules.
- Open the live page in a private window and confirm the slot renders (ad blockers may hide the creative).
- After traffic, open Analytics → Ad embed and compare renders by placement and day range.
- Remove or relocate low-value zones—especially on image-heavy portfolio pages.
What you'll see
Configured placements listed under Integrations; live pages show the iframe slot when the provider allows delivery. Analytics → Ad embed summarizes total renders, unique visitors, a timeseries, and top placements.
Ad blockers and policy
Blocked creatives undercount renders—treat metrics as directional. Keep a short compliance note per network; ArtInStack does not guarantee ad approval or revenue.
Density on portfolio pages
Too many zones on a single gallery page hurts UX and SEO—prefer one in-content zone plus an optional header slot.
Verifying your setup
- Provider fields and at least one placement are saved under Integrations.
- An Ad embed block on a published page references that placement.
- Analytics → Ad embed shows render activity after real visits (when ads are enabled).