Trigger Ideas — Channel Performance Signals

These triggers are driven by data from connected channels (GSC, Google Analytics, Google Ads, Facebook, GBP, AI Visibility). All the underlying data already flows into Leadmetrics — these ideas just need a scheduler check and a post-creation hook.

9. Website Traffic Spike

Signal: Google Analytics daily sessions exceed the 30-day rolling average by more than 25% for two consecutive days.

Post angle: Find the source of the spike (top referrer, top landing page, top search term from that period) and create a “what’s driving our traffic right now” post — educational content that capitalises on the moment. Example: “Our article on [topic] is getting a lot of traffic this week — here’s the short version.”

Why it works: A traffic spike usually means something in the market shifted — a news event, a viral mention, a competitor disappearing, or seasonal demand. Publishing during the spike puts the brand in front of the audience at exactly the right moment. It’s also rare enough that clients find it exciting and are motivated to act quickly.

Automation level: AI identifies the spike + the top traffic source and drafts a post angle. Needs human approval — the spike source needs editorial judgment (is it a referral spam bot, or a genuine moment?).

Dedup window: Once per 14-day window (ignore smaller follow-on spikes after the first trigger).

Data source: Google Analytics channel — ConnectedChannel + GA insight worker data. The insight workers already track page views and traffic sources.

Implementation sketch:

• Extend the GA insight worker to compare today’s session count vs the 30-day average
• If >25% above average: flag TriggerOpportunity { type: "traffic_spike", tenantId, channelId, metadata: { topPage, topReferrer, sessionCount, avgSessions } }
• Surface in DM portal “Performance Moments” section + dashboard widget
• Writer receives: top landing page URL, page title, traffic delta, top referrer → generates educational teaser post for that content
• If spike is from a search query, post angle pivots to “People are searching for [query] — here’s our take”

SCENE_MAP entry (traffic_spike):

“Data-forward editorial design with an upward trending line or bar chart visual, clean and modern, brand colours on a light background, metric highlighted as the headline — conveys momentum without being boastful”

10. Ad Campaign Conversion Milestone

Signal: Google Ads or Facebook/Meta Ads conversion count for the current calendar month crosses a round-number milestone (first 10, 50, 100, 500, 1000 conversions from paid channels).

Post angle: “We’ve driven [N] [leads/sign-ups/sales] this month through [platform] — here’s what we’ve learned about what makes our audience click.” Educational, performance-proof post.

Why it works: Paid performance proof builds brand credibility in a way that organic posts rarely achieve. It signals that real people are choosing the brand. The educational angle (“what made the audience click”) adds value beyond self-promotion.

Automation level: Fully automatic once the threshold detection is in place. The post angle is templated enough that the writer can execute it with just the conversion count, platform name, and top-performing ad headline as context.

Dedup window: Once per milestone tier, per channel, per calendar month.

Data source: Google Ads + Facebook Ads channel sync (already connected for many tenants).

Implementation sketch:

• New ad-milestone.ts scheduler handler (weekly)
• Query Ads channel data for current-month conversion count
• Compare to milestone tiers; check if the threshold was crossed since last check
• Store lastAdMilestone__<tenantId>__<channelId> in a per-tenant metadata field
• Writer context: platform, conversion count, month, top-performing ad headline + description, conversion type (lead/sale/signup)
• contentType: "ad_milestone" → proud but educational, specific about platform

SCENE_MAP entry (ad_milestone):

“Professional performance-marketing visual — bold conversion number as hero, subtle platform logo watermark (Google/Meta), clean metric card aesthetic, brand colours, confidence-forward”

11. AI Visibility Score Jump

Signal: The tenant’s GEO score (from the ai-visibility-monitor worker) rises by more than 10 points week-over-week, or the brand first achieves a citation in a new AI platform (ChatGPT, Gemini, Perplexity, Claude).

Post angle: “Our brand is now showing up in AI search results — here’s what it means and why it matters for [industry].” Thought leadership on the AI search shift, with the brand as a concrete example of it working.

Why it works: AI search visibility is a new and poorly understood topic that most brands haven’t acted on yet. A brand that can say “yes, we appear when people ask ChatGPT about [topic]” has a genuine differentiator — and posting about it positions them as early adopters and thought leaders in the AI era.

Automation level: Fully automatic — ai-visibility-monitor already runs and stores scores per tenant per platform. A completion hook can detect score jumps.

Dedup window: Once per 10-point band crossed (fire at 30, 40, 50, 60, 70, 80); once per new AI platform first-citation.

Data source: AIVisibilityMonitor results stored in DB (existing); ConnectedChannel metadata for score history.

Implementation sketch:

• In ai-visibility-monitor worker completion handler: compare new score to previous score
• If delta ≥ 10 points OR if a new AI platform returned a citation for the first time: enqueue a social post trigger
• Writer context: overall GEO score, delta, list of AI platforms now citing the brand, brand’s main keyword themes → thought leadership tone, slightly technical but accessible
• contentType: "ai_visibility" in social-post-writer

SCENE_MAP entry (ai_visibility):

“Futuristic-but-approachable design — AI/search motif (chat bubble, neural network, or search interface element), brand colours, clean tech aesthetic, forward-looking and confident”

12. Blog Post SEO Score Improvement

Signal: A BlogPost.seoScore rises above 80 after a revision run by the seo-optimizer worker — especially if it previously scored below 60 (a significant uplift).

Post angle: “We just optimised our article on [topic] for AI search. Here’s the updated version — and what changed.” Honest, behind-the-scenes content that demonstrates continuous improvement and drives re-engagement with existing content.

Why it works: Most brands never revisit published content. Announcing an update signals quality and gives an existing article a second organic reach moment without starting from scratch. It also educates the audience on how AI search optimisation works, which is increasingly relevant.

Automation level: Fully automatic — hook into seo-optimizer worker completion.

Dedup window: Once per blog post per 60-day window (don’t resurface the same post repeatedly).

Data source: BlogPost.seoScore + BlogPost.seoAnalysis (existing fields populated by seo-optimizer worker).

Implementation sketch:

• In seo-optimizer worker completion handler: if new score ≥ 80 AND (previous score was null OR previous score < 70): fire social trigger
• Writer context: blog post title, updated seoScore, top 2–3 improvements made (from seoAnalysis), link to the post
• contentType: "content_update" → confident, improvement-focused, invites re-read
• Relevant for LinkedIn (thought leadership on SEO/AI), Facebook (article reshare), and X (thread on what changed)

SCENE_MAP entry (content_update):

“Editorial blog-style graphic — ‘Updated’ badge or stamp element, article title as headline, subtle ‘before/after’ or improvement indicator, clean and professional, knowledge-forward”