name and a websiteUrl (the click destination). Everything else
about the creative is up to you. Custom fields let you ask advertisers for a tagline, a banner image,
a button label, a discount code, or whatever your layout needs.
Advertisers fill in your fields when they submit creative, you see the values in the review queue,
and your renderer reads them back from the served ad. Manage fields under Fields.
Field types
Each field also has:
- Required: whether the advertiser must fill it in.
- Publisher only: hide it from the advertiser’s form and set the value yourself. See below.
- Help text, Placeholder and Default: guidance and a pre-filled value.
Publisher-only fields
Some values are yours to set, not the advertiser’s: an editor’s pick, a curated blurb, a category you assign. Turn on Publisher only and the field disappears from the advertiser’s creative form while staying editable by you on the ad’s page. The value still serves inad.meta exactly like any other field, so your renderer reads it the same
way. That also means it is not private: anything in ad.meta is public. And a publisher-only
field can’t be Required, since advertisers never see it.
The slug
When you create a field, Revinel assigns it a stable machine key called a slug (for example a “Banner image” field getsbannerImage). The slug is what your code reads:
@revinel/sdk typed meta section for typesafe access, and
Serving ads for how the served ad is shaped.
Tips
- Keep the required set small. Every required field is friction at checkout.
- Use an Image field for logos and banners rather than asking for a URL. The upload is validated and hosted for you.
- Name fields for what they are in your layout, not for a specific advertiser. You are defining a template every advertiser fills in.