When your agency launches hundreds or thousands of ads, rebuilding the same setup for every batch is wasted work. Kitchn Ad Templates let your team save reusable ad components and apply them across selected ads when they are needed.
Recurring campaigns rarely start from zero. The headlines may be familiar. Tracking may follow the same structure. Destination URLs, product sets or forms may already be known.
Ad Templates let your team save those reusable components and bring them into future launches instead of setting them up again manually. Templates can include fields such as:
And other supported ad attributes.

Templates aren't silently inherited by every new ad. Your media buyer chooses when they should be applied.
Select the relevant rows in the Launch Sheet, choose the template and apply its saved attributes across the selection in bulk.
That gives teams the speed of standardisation without removing control from the buyer running the launch.

Already built something you want the rest of the team to reuse? Create an Ad Template from an existing ad and save the relevant fields for future launches.
Instead of documenting a working setup somewhere else and hoping everybody recreates it correctly, make the setup itself reusable.
Templates can be organised and reused across the organisation, with platform-specific templates and folders for keeping different setups structured.
Kitchn also supports CSV import and export for Ad Templates, making larger template libraries easier to manage. Templates can be shared across accounts or restricted to a specific ad account where needed.
Ad Templates are particularly useful when your team is handling:
Kitchn doesn't automatically inherit every Ad Template into every new row. Templates are applied deliberately through bulk actions or configured workflows.
That's important for agencies: standardisation should remove repetitive work without quietly applying the wrong client setup to the wrong launch.
Your best media buyers shouldn't spend their day recreating settings they've already built dozens of times before.
Save them once.
Reuse them when they're relevant.
Keep the team moving as launch volume grows.