Elysia Tools
Navigation
Workflow Playbook
Prepare campaign URLs, reconcile UTM parameters, deploy an optional self-hosted short link, scan final QR artwork and deliver a reviewed placement ledger.
Hubs
This playbook is for campaign operators and event teams delivering one reviewed placement kit. The result is an approved URL per placement, final QR artwork, any deployed redirect mapping and a ledger connecting them. It is not a barcode inventory project or a technical SEO indexation audit. List the landing page, channel, creative variant, owner and approved source, medium and campaign values before generating anything.
Keep a clean original URL and inspect host, path, query and fragment. Static URL validation and structural phishing checks neither contact the site nor certify safety. A restrictive format warning is not permission to delete a necessary character. Ask the owner to resolve unfamiliar domains, special characters or private links. Do not upload secrets or put customer identifiers in public tracking fields.
Use the parameter builder for deliberate assembly and the query analyzer for comparisons across placements. Preserve business parameters such as product or language selection. Query values belong before the fragment; do not bury UTM values inside a page anchor. Avoid pre-encoding complete values and then encoding them again. Keep the raw URL as evidence: extraction may apply extra decoding, and analyzer warnings are hints rather than a complete encoding audit. If parsing fails or a value is ambiguous, stop and reconcile against the intended landing behavior.
The bundle requires source, medium and campaign, optionally lowercases values and removes existing utm_* keys before setting the new values. These are tool rules, not proof that an analytics property is configured. Review replacement and case changes explicitly, including content, term and campaign ID when used. A poster and an email may share a campaign but need distinct agreed placement values.
For example, keep utm_campaign=autumn-launch for the whole campaign and use utm_content=poster-a versus utm_content=poster-b to distinguish approved variants. Agree source and medium separately for each channel; these illustrative values do not register a channel grouping in your analytics property.
The bundle produces full and short URLs, two QR PNGs, redirect snippets and a CSV row; it does not deploy a service. Its automatic slug is derived from a 32-bit hash, not a collision-free reservation. Custom slugs are sanitized. Review the final slug against existing mappings, retain the exact destination and never silently overwrite another active campaign. The short-domain input supplies a hostname, not a subpath-hosting configuration.
The infrastructure owner must adapt the chosen snippet to the actual server syntax, escaping, existing rules and HTTPS setup, then test it in the receiving environment. Do not paste arbitrary destination strings into server configuration without review. Test the entire live chain for loops, unexpected hosts and lost query values. If ownership or deployment is unavailable, use the approved full tracked URL rather than ship a QR pointing to an unconfigured domain.
Decode the exact QR used in the design and compare its payload with the ledger. If using a short QR, its payload is the short URL, so compare the mapping separately. Keep clear margins, adequate contrast and usable physical size. A successful decode of the source PNG does not approve a resized, cropped, recolored or printed variant. Scan the final export and a physical proof where relevant with representative devices, then follow the actual route and verify destination behavior.
Test analytics receipt separately with authorized access and record consent conditions and observation time. If it cannot be checked, label it unverified rather than claiming attribution. Add headers to the generated CSV row and extend the ledger with placement, asset revision, mapping owner and separate scan, redirect and analytics outcomes. CSV validation checks structure, not duplicate campaign assignments, formula safety or correctness of business values; review those manually before spreadsheet use. Store assets and reviewed configurations locally, retain exceptions, and reapprove changed links or artwork. Use the related DNS/HTTPS workflow for infrastructure failures and the general QR workflow for non-campaign labels.
The generated row has nine fields in this order: date,campaign,source,medium,content,term,id,short_url,full_url. Use matching headers or explicitly map them to your own schema before adding review columns.
Workflow playbook
Review URL structure, suspicious hosts and existing query or fragment values. Keep the original URL and resolve warnings with the destination owner; static checks do not test availability.
Construct approved query values without manual concatenation, then compare the placement URL set for naming drift and encoding warnings. Check raw URLs too; analysis is not exhaustive.
Build the UTM bundle and retain its normalization warnings, full URL, CSV row and QR pair. Use the standalone QR generator only for an approved alternative payload or size; deploy reviewed redirect configuration outside the tool if using short links.
Decode the delivered QR and compare the complete payload. Then scan on representative devices, follow the deployed route and inspect landing parameters; verify analytics receipt separately where access permits.
Use the full tracked URL when no redirect owner is available. A short link needs domain control, HTTPS, reviewed deployment and an explicit slug-to-destination register.
Preserve required product parameters and fragments. The bundle replaces existing utm_* keys, so reconcile them with the campaign owner before generation rather than silently mixing campaigns.
Approve only after scanning the final artwork and checking the live route. Keep analytics receipt as a separate test; a decoded URL alone does not prove attribution.
Assemble the generated row with matching headers and placement, asset version, redirect owner and review results. Validate CSV syntax, compare recorded URLs, manually resolve duplicates and retain the approved files with exceptions.