Help Center

Single URL: Use this mode when you need one final campaign link. Enter the landing page URL, fill the required UTM fields, add optional breakdown fields if needed, then copy the finished tagged URL. This is the fastest option for one-off creatives, placements, or QA checks.

Bulk URLs: Use this mode when you need to generate many UTM-tagged URLs at once. Paste CSV or tab-separated rows, keep the default column order or provide a custom header, then copy all valid URLs or export them as CSV. It is useful for campaign matrices, multi-size creative sets, and trafficking sheets.

Publisher Patterns: Use this mode when the advertiser landing page also needs publisher-side dynamic values appended as query parameters. The tool adds pattern placeholders such as `%%PATTERN:brand%%` so page-level values can be passed through the ad request from the publisher to the advertiser.

Landing page URL: Enter the final advertiser landing page. Existing non-UTM query parameters are preserved, and the builder adds or replaces only the UTM parameters. This helps keep the destination clean while still applying campaign tracking consistently.

Required campaign fields: `utm_source`, `utm_medium`, and `utm_campaign` are required because they are the minimum fields most trafficking and reporting setups rely on. If these are missing, the generated URL is not complete enough for standard campaign tracking.

Optional breakdown fields: Use `utm_id`, `utm_term`, and `utm_content` for internal IDs, audience or keyword notes, and creative or placement-level reporting. These are useful when the same campaign needs more granular reporting by variant or audience.

Generated URL: Shows the finished campaign URL as soon as the required fields are valid. Use it to confirm the final structure before copying it into a tag sheet, ad server, or QA document.

Copy URL and Reset: Copy saves the finished tagged link to the clipboard. Reset clears the landing page and all UTM values so you can start again with a fresh build.

Paste bulk rows: Paste CSV or tab-separated rows to generate many tagged URLs in one batch. The builder accepts either a header row or the default order `url, source, medium, campaign, content`, so it can fit both structured spreadsheets and quick copy-paste workflows.

Custom header: Use the custom header helper when your spreadsheet columns are in a different order. You can choose supported columns, reorder them, and insert the header into the first line so the parser maps each value correctly.

Bulk output: Valid rows are converted into tagged URLs immediately. You can switch between URLs-only output for copying and table view for QA, depending on whether you are preparing delivery output or reviewing row-level details.

Copy all URLs and Download CSV: Copy all URLs saves every valid generated link as a newline-separated list. Download CSV keeps the main input columns and adds a `generated_url` column, which is useful when you want to return the results to a spreadsheet or trafficking sheet.

Row preview and errors: Rows with missing required values or invalid URLs are flagged separately so valid rows can still be generated. Use row preview to spot-check results before copying or downloading the final batch.

Input requirements: Bulk mode requires `url`, `source`, `medium`, and `campaign`. Optional columns are `id`, `term`, and `content`. Keeping this structure consistent makes repeated bulk generation much faster.

Landing page URL: Use the final advertiser landing page for the ad creative. The tool appends publisher pattern placeholders to this URL so page-level values can be passed later through the ad request. This is useful when the advertiser wants contextual or page-derived signals carried into the destination URL.

Publisher presets: Built-in presets ship with the tool. Local presets are saved only in the current browser, so they can be removed if browser cookies or site data are cleared. Use presets when the same publisher key-pattern mapping is reused often.

Editable keys and patterns: Each row defines the custom-targeting key expected in the ad request and the corresponding Google Ad Manager pattern macro inserted into the final URL. Use this when a publisher passes values such as brand, model, category, or dealer identifiers dynamically.

Add row, Remove, Save preset, and Delete preset: Add row creates another key-pattern pair. Remove deletes a row. Save preset stores the current mapping locally in the browser, and Delete preset removes the selected local preset. This keeps repeated publisher-specific setups easy to reuse without rebuilding them each time.

Generated URL and Copy URL: The finished output shows the landing page with all configured publisher pattern placeholders appended as query parameters. Copy URL saves that link to the clipboard so it can be used in trafficking or shared with the advertiser.

Naming consistency: The builder does not enforce a taxonomy, so keep source, medium, campaign, and content naming consistent across publishers, placements, and creative versions. A clean naming system matters as much as the URL structure itself.

Query parameter behavior: Existing non-UTM query parameters are preserved. Only UTM keys are added or replaced, which helps avoid breaking landing pages that already depend on their own query values.

Bulk row errors: Rows with invalid URLs or missing required fields are flagged separately so valid rows can still be generated and copied. This makes it easier to fix only the broken rows instead of rebuilding the whole batch.