Tell Us What to Track: Your Custom Event Spec Sheet

You know your store needs tracking. You know what you want to measure — newsletter signups, video plays, wholesale inquiries. But when we ask “what events do you need?”, the answer is usually “um… everything?” This tool fixes that. Fill out the form below, and you’ll get a clean, structured spec sheet that tells us exactly what to build.

Why We Need This

Every custom tracking setup starts with the same conversation:

Us: “What do you want to track?”
You: “Um… when people sign up for the newsletter? And maybe when they watch the video?”
Us: “Okay, what should we call those events? What data should they carry?”
You: ”…I don’t know, you’re the experts?”

This back-and-forth can take days. The spec sheet below cuts it to 15 minutes. You tell us what happened and where, we handle the technical translation.

How to Name Events (The Rules)

Before you start filling out the form, here are the naming rules we follow:

1. Lowercase + snake_case — newsletter_signup, not Newsletter-Signup or newsletterSignup
2. Verb/noun phrases — add_to_cart, not just cart
3. No spaces or Chinese characters — product_view, not product view or 产品浏览
4. Prefer standard events — If GA4/Meta/TikTok already have a standard event for it (like add_to_cart), use that name. Only create custom events when standard ones don’t cover your needs.

Not sure what the standard events are called on each platform? See the complete event name mapping →

Build Your Event Spec Sheet

Fill out the form below. Your work is automatically saved in your browser (localStorage) — if you close the tab and come back later, it’ll still be here. When you’re done, click Copy Markdown to paste it into an email or WeChat message, or Download CSV to save it as a spreadsheet.

Note: This is a demo tool. Nothing you enter is uploaded to any server — it stays in your browser. If you clear your browser cache or use a different device, your work will be lost. Make sure to copy or download before you leave.

Prefer Excel?

If you’d rather fill this out in Excel, download our template:

Download Event Spec Template (Excel)

The template includes:

• Pre-filled examples (newsletter signup, video play, wholesale inquiry, add to cart)
• Naming rules reference sheet
• Empty rows for your custom events

Fill it out and send it to us via email or WeChat.

What Happens Next

Once you send us your spec sheet, here’s what we do:

1. Review — We check for naming conflicts, missing parameters, and platform compatibility
2. Map — We translate your events into platform-specific implementations (GA4 generate_lead, Meta Lead, TikTok Subscribe, etc.)
3. Build — We implement the tracking code, test it in each platform’s debug tool, and verify it fires correctly
4. Document — You get a final spec sheet with screenshots showing each event firing in GA4 DebugView, Meta Events Manager, and TikTok Events Manager

The whole process typically takes 2-3 days from spec sheet to production.

Running a headless storefront? The implementation is different — see what changes in headless tracking →

Examples

Here are four real examples from past projects:

#	Trigger	Page/Location	Event Name	Parameters	Platforms	Type	Acceptance Criteria
1	Click “Subscribe Newsletter” button successfully	Homepage popup	newsletter_signup	page, source	GA4 + Meta (Lead)	Custom	Lead event visible in Events Manager
2	Video watched over 50%	Product page	video_play_50	video_id, product_id	GA4	Custom	Visible in DebugView
3	Wholesale inquiry form submitted	/wholesale	wholesale_inquiry	form_id, product_count	GA4 + Meta (Lead)	Custom	Conversion test passed
4	Add to cart	Site-wide	add_to_cart (standard)	items, value, currency	GA4 + Meta + TikTok	Standard	—

Notice the pattern: what happened (trigger), where (page), what to call it (event name), what data to carry (parameters), where to send it (platforms), and how to verify it works (acceptance criteria).

FAQ

Do I need to fill out every column?

Yes — but don’t overthink it. If you’re not sure what parameters an event should carry, just write “product info” or “form data” and we’ll translate that into the technical fields. The most important columns are Trigger (what happened) and Event Name (what to call it).

What if I don't know the event name?

Just describe what happened in plain language — “user submits contact form” or “customer adds product to wishlist” — and we’ll suggest the proper snake_case event name. That’s our job.

Should I use standard events or custom events?

If GA4, Meta, or TikTok already has a standard event for what you’re tracking (like add_to_cart, purchase, generate_lead), use that. Standard events get better reporting, better optimization, and better audience building. Only create custom events when standard ones don’t exist — like video_play_50 or wholesale_inquiry.

What happens to my data if I close the browser?

Your work is saved in your browser’s localStorage, so if you close the tab and come back later (same browser, same device), it’ll still be here. But if you clear your browser cache, use incognito mode, or switch devices, your work will be lost. Always copy or download before you leave.

---

This tool is part of our event tracking setup process. Once you send us your spec sheet, we’ll review it, map it to platform-specific implementations, and build the tracking code. Questions? Talk to us.