Freemium sounds right. I'd hope that anything I contribute to the free/open parts of the community stay free, but willing to pay for gated parts of the community that provide more value.

@Camila Reyes I just recently setup TikTok and Meta pixels up through GTM as well. It took me 2 days but I didn't need to hire anybody, I just had Cursor walk me through it step by step. The biggest challenge was configuring things in GTM itself, because it doesn't seem to have a CLI or API you can use to programmatically do it, so you have to go through the UI. I captured a best-practices doc for myself, which I've summarized here. Give this to your developer or feed this into your vibe-coding tool, and it may help you steer you in the right direction.. 😀 - Use TikTok’s Events Manager → Test Events to validate in real time. Don’t rely on the main Events tab; it can lag 15–120 minutes. - Use GTM Preview against "localhost" / staging. Iterate without publishing each change; publish only once everything fires cleanly. - Standardize your dataLayer. Push the same structure for all platforms (GA4, TikTok, Meta). Example for leads: event: "email_signup", form_id, form_location, form_title, timestamp, sha256_email (hashed client-side). - Single Page App (SPA) gotcha: page views don’t auto-fire on route changes. Add a small client component that pushes page_view whenever the path/search changes. - TikTok base pixel must load before event tags. Either use the template + base tag or paste the pixel snippet as a Custom HTML tag on All Pages so ttq is defined. - Advanced Matching (AAM) matters. Hash the email (SHA-256) on submit, push it to the dataLayer, and map it to TikTok’s “SHA256 Hashed Email” field (don’t send it as a custom property). - Prevent early redirects. If your form redirects immediately, intercept submit, push the event (and hash), then resume form.submit() so the event lands before navigation. - Next.js tip: if you use useSearchParams, wrap the client component in <Suspense> (otherwise static builds can fail). - After going live, give platforms time. Test Events are instant; production dashboards can take up to 2 hours to reflect the first standard event