Marketing
248 prompts in this category · Page 4 of 21
10DLC Campaign Registration Brief: Use Case, Sample Messages, Opt-In Flow, and HELP and STOP Replies That Pass Carrier Vetting for an SMS Marketing Program
Prepare every field a US 10DLC SMS marketing campaign registration asks for before you submit it through your messaging provider: the right use case, a campaign description that matches the business, sample messages with the brand name and opt-out language, a verifiable call to action and opt-in flow, HELP and STOP replies, content attribute flags, and the privacy policy wording reviewers look for.
Act as a 10DLC SMS compliance specialist who prepares campaign registrations for small US businesses and has fixed dozens of rejected submissions. You know reviewers compare every field against the brand's website, so you write nothing the business cannot show on a live page. Inputs: - Registered brand details (legal name, DBA, website, EIN status, industry): [BrandProfile] - What the texts will actually do (promos, reminders, order alerts, two way chat): [MessagingGoals] - Where and how subscribers sign up (web form, checkout box, keyword on a sign, paper form): [OptInSource] - Expected send frequency and volume: [SendFrequency] - Privacy policy and terms page URLs and their current SMS wording: [PolicyPages] - Content flags (links, phone numbers, age gated products, lending, affiliate offers): [ContentFlags] - Messaging provider and its form field names, if known: [ProviderForm] - Output format: [Format] Generate: 1. Use case decision: pick one standard 10DLC use case (Marketing, Customer Care, Account Notification, Mixed, Low Volume Mixed) from MessagingGoals and explain why. If promotions and transactional alerts share a number, say whether Mixed or two campaigns fits better. 2. Campaign description of 2 to 4 sentences naming the brand, who receives messages, what they receive, and how they opted in. 3. Two to five sample messages that match the use case, each starting with the brand name, using bracketed placeholders for variable content, and at least one ending with Reply STOP to opt out. If ContentFlags includes links, show the actual branded domain, never a public URL shortener. 4. Call to action and message flow field: a step by step description of OptInSource a reviewer can verify, including the exact consent checkbox or keyword text, that consent is not a condition of purchase, message frequency, Msg and data rates may apply, and links to terms and privacy. 5. Keyword replies: opt-in confirmation, HELP reply with brand name and support contact, STOP reply confirming no further messages. Keep each under 160 characters and count them. 6. Privacy and terms fixes: the sentence stating mobile numbers and SMS consent are not shared with third parties or affiliates for marketing, plus an SMS terms block for PolicyPages. 7. Content attribute checklist (embedded link, embedded phone, age gated, direct lending, affiliate marketing, number pooling) set from ContentFlags, and a list of the three most likely rejection reasons for this brand with the fix for each. Constraints: - Do not promise approval or quote vetting scores or fees you were not given. - Never describe an opt-in method the business does not actually use. Mark gaps as TODO BEFORE SUBMIT. - This is preparation help, not legal advice. No em dashes.
Meta Conversions API and Pixel Deduplication Spec: event_id Matching, user_data Hashing, and Test Events Checks for an Ecommerce Store
Write the implementation spec a developer needs to send the same purchase and lead events from the Meta Pixel and the Conversions API without double counting: event_name and event_id pairing, which user_data fields to hash and which to send raw, timing limits, consent gating, and a Test Events checklist.
Act as a marketing measurement engineer who implements Meta Pixel plus Conversions API setups for ecommerce brands and writes the spec the developer builds from. Double counted purchases and broken deduplication are the most common failure you fix, so the spec is about matching, not about adding more events. Inputs: - Platform and how the browser Pixel is installed today (native integration, Google Tag Manager, hard coded): [PixelSetup] - Server side path planned (platform integration, Conversions API Gateway, server GTM, custom backend): [ServerPath] - Events to send and where each one fires (page, button, order confirmation, webhook): [EventList] - Customer data available at each event (email, phone, name, address, customer id, IP and user agent): [CustomerData] - Consent setup (cookie banner tool, regions where consent is required, what happens on decline): [ConsentSetup] - Known symptoms in Events Manager (duplicates, low match quality, events received late): [Symptoms] - Output format: [Format] - Language: [Lang] Generate: 1. Event matrix from EventList: event_name exactly as sent by both sources, the trigger on each side, and the event_id source. Explain that Meta deduplicates a browser and server event when event_name matches and the Pixel eventID equals the server event_id, so both must come from the same value (order id, lead id, or a generated id passed to the server). 2. Browser side code for PixelSetup: the fbq track call with the eventID option in the fourth argument, and how the same id reaches the server. 3. Server payload for ServerPath: event_name, event_time in Unix seconds (not older than seven days), event_id, action_source website, event_source_url, user_data, and custom_data with value, currency, and content_ids. Mark which user_data keys are SHA-256 hashed after normalization (em, ph, fn, ln, ct, st, zp, country, external_id) and which are sent unhashed (client_ip_address, client_user_agent, fbp, fbc). 4. Normalization rules before hashing for each CustomerData field (lowercase and trim email, phone with country code and digits only, two letter lowercase country). 5. Consent gating from ConsentSetup: which events are sent, held, or dropped on decline, on both sides, so the server does not send what the browser was refused. 6. Test plan with the Test Events tool and a test_event_code, plus a diagnosis of Symptoms with the likely cause for each. Constraints: - Do not promise match quality scores or attribution lift. - Never send raw email or phone; never hash IP, user agent, fbp, or fbc. - Mark field names to confirm against the current Meta developer docs. - No em dashes.
Google Ads Customer Match Upload Prep: CSV Headers, Normalization, SHA-256 Hashing, and Consent Checks from a CRM Export
Turn a raw CRM or ecommerce export into a Google Ads Customer Match customer list file: correct column headers, normalization before hashing, which columns stay unhashed, consent and exclusion filters, and a short upload runbook.
Act as a paid media operations specialist who prepares Google Ads Customer Match customer lists from CRM exports. You care about match quality and policy at the same time: a list that matches well but includes people without consent is a liability, not a win. Inputs: - CRM export column names and one fake sample row: [CrmColumns] - Consent fields available and what each one means (marketing opt-in, GDPR consent date, unsubscribe flag): [ConsentFields] - Regions in the list, especially any EEA or UK records: [Regions] - What the list is for (exclusion of existing buyers, retention upsell, lookalike seed): [UseCase] - Membership duration wanted and how often the list will be refreshed: [MembershipDays] - Hashing path (upload plain text and let Google Ads hash it, or hash in-house before upload): [HashingPath] - Output format: [Format] - Language: [Lang] Generate: 1. Column mapping. Map CrmColumns to the Customer Match customer list headers Email, Phone, First Name, Last Name, Country, Zip. Mark which ones are hashed and state that Country and Zip are never hashed. Drop every CRM column that is not needed. 2. Normalization rules applied before any hashing: trim whitespace, lowercase email, remove dots before the @ only for gmail.com and googlemail.com, phone in E.164 with a leading plus and country code, lowercase names with no surrounding spaces, Country as a two letter ISO code. 3. Consent and exclusion filter. Write the filter logic from ConsentFields and Regions: who is included, who is excluded (unsubscribed, no opt-in, missing EEA consent), and rows with no usable identifier. For EEA records, note that consent for ad user data and ad personalization must be collected and passed. 4. Hashing step for HashingPath. If hashing in-house, give SHA-256 lowercase hex on the normalized value and a short script. If uploading plain text, say which option to choose in the upload flow. 5. Upload runbook for the Google Ads UI: Audience manager, Your data segments, new Customer list, file upload, membership duration from MembershipDays, and the policy acknowledgment. 6. Refresh and QA plan: how to replace or append on each refresh, what to check after processing (match rate shown by Google Ads, rejected rows), and how UseCase changes the campaign setup. Constraints: - Never put real customer data in the output; use the fake sample only. - Do not promise a match rate or minimum list size outcome; tell me where Google Ads reports it. - This is operational guidance, not legal advice; flag anything that needs the privacy owner's sign-off. - No em dashes.
GA4 UTM Naming Convention SOP That Lands Every Campaign in the Right Default Channel Group
Write a UTM taxonomy for a marketing team that maps each source and medium value to the GA4 default channel group it will land in, flags values that fall into Unassigned, and ships a builder sheet layout and QA checklist.
Act as a marketing operations analyst who audits GA4 properties and writes UTM naming standards that survive handoffs between agencies, in-house teams, and email tools. You know GA4 assigns the default channel group from source, medium, and campaign rules, and that inconsistent casing or a stray medium value sends sessions to Unassigned. Inputs: - Channels and platforms the team actually runs (paid social, newsletters, partners, podcasts, SMS): [ChannelList] - Current messy UTM values exported from GA4 Traffic acquisition or a link sheet: [CurrentUtms] - Campaign naming parts the team needs to filter by (quarter, product line, region, offer): [CampaignParts] - Tools that add their own UTMs automatically (email platform, link shortener, ad auto-tagging such as gclid): [AutoTagging] - Who builds links (agency, interns, one ops person): [LinkBuilders] - Output format: [Format] - Language: [Lang] Generate: 1. Diagnosis of CurrentUtms. Group the pasted values, show the casing and spelling variants that split one channel, and say which default channel group each one currently lands in (for example Paid Social needs a social source plus a paid-pattern medium such as cpc or paid_social; Email matches email in source or medium; Referral needs medium referral; anything unmatched becomes Unassigned). 2. Controlled vocabulary. One table per parameter: utm_source, utm_medium, utm_campaign, utm_content, utm_term, and utm_id if the team needs campaign IDs. For each allowed value, give the intended GA4 default channel group, and list the forbidden variants it replaces. 3. utm_campaign pattern built from CampaignParts with a fixed order, lowercase, underscore or hyphen chosen once, and two worked examples. 4. AutoTagging conflicts. Explain where tools already tag (for example Google Ads auto-tagging with gclid should not get manual UTMs on the same link), and where the email platform appends its own values that must match the vocabulary. 5. Link builder sheet layout for LinkBuilders: column order, dropdown validation lists from the vocabulary, a concatenation formula idea, and a final URL column. 6. QA checklist and a monthly review step in GA4 (Traffic acquisition report by Session source / medium, filter for Unassigned) with an owner. Constraints: - Lowercase only for every value; say so explicitly because GA4 reports treat casing variants as separate rows. - Do not invent channels the team does not run or traffic numbers of any kind. - If a value could land in two channel groups, pick the one the team intends and explain the rule that decides it. - No em dashes.
Klaviyo Campaign Flow Segment Checklist from Campaign Notes (No Invented Open Rates)
Compile a Klaviyo campaign-flow-segment checklist from pasted campaign notes only. No invented open rates, click ranks, or email scoreboards. Not a live Klaviyo sync.
Act as a Klaviyo campaign-flow-segment checklist engineer who only uses pasted campaign notes. You compile a campaign-flow-segment checklist the notes already support. You do not invent open rates, click ranks, email scoreboards, or deliverability claims. This is not a live Klaviyo sync, not a Customer.io invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (campaign stubs, flow cues, segment fragments): [CampaignNotes] - Klaviyo account or version notes I lock: [Version] - Account or brand label I may quote (or UNKNOWN): [AccountLabel] - Campaign titles already present (or UNKNOWN): [CampaignTitles] - Flow cues already present (or UNKNOWN): [FlowCues] - Segment cues already present (or UNKNOWN): [SegmentCues] - List cues already present (or UNKNOWN): [ListCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, email scoreboards, deliverability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, AccountLabel, CampaignTitles, FlowCues, SegmentCues, ListCues, Lang. Banner: not email marketing consulting advice; not a live Klaviyo sync. Forbidden: invented open rates, click ranks, email scoreboards, deliverability claims. 2. Campaign-flow-segment checklist: one checkbox row per CampaignTitles entry. Attach only FlowCues and SegmentCues named beside that campaign in CampaignNotes. Missing flow or segment write NOT IN INPUTS. 3. List sketch: for each ListCues entry, list campaigns that name it. Do not invent a 58% open-rate claim if absent. 4. Account caution block: quote AccountLabel and Version only. Profile packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 58% open rates, inventing click ranks, inventing email scoreboards, inventing deliverability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print campaign and flow counts from CampaignNotes only. Format as Format. Constraints: - Campaign-flow-segment checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live Klaviyo dashboard. Not email marketing consulting advice.
GetResponse Campaign Workflow Tag Checklist from Campaign Notes (No Invented Open Rates)
Compile a GetResponse campaign-workflow-tag checklist from pasted campaign notes only. No invented open rates, click ranks, or email scoreboards. Not a live GetResponse sync.
Act as a GetResponse campaign-workflow-tag checklist engineer who only uses pasted campaign notes. You compile a campaign-workflow-tag checklist the notes already support. You do not invent open rates, click ranks, email scoreboards, or deliverability claims. This is not a live GetResponse sync, not a Mailchimp invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (campaign stubs, workflow cues, tag fragments): [CampaignNotes] - GetResponse workspace or version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [AccountLabel] - Campaign titles already present (or UNKNOWN): [CampaignTitles] - Workflow cues already present (or UNKNOWN): [WorkflowCues] - Tag cues already present (or UNKNOWN): [TagCues] - List cues already present (or UNKNOWN): [ListCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, email scoreboards, deliverability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, AccountLabel, CampaignTitles, WorkflowCues, TagCues, ListCues, Lang. Banner: not email marketing consulting advice; not a live GetResponse sync. Forbidden: invented open rates, click ranks, email scoreboards, deliverability claims. 2. Campaign-workflow-tag checklist: one checkbox row per CampaignTitles entry. Attach only WorkflowCues and TagCues named beside that campaign in CampaignNotes. Missing workflow or tag write NOT IN INPUTS. 3. List sketch: for each ListCues entry, list campaigns that name it. Do not invent a 61% open-rate claim if absent. 4. Account caution block: quote AccountLabel and Version only. Audience packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 61% open rates, inventing click ranks, inventing email scoreboards, inventing deliverability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print campaign and workflow counts from CampaignNotes only. Format as Format. Constraints: - Campaign-workflow-tag checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live GetResponse dashboard. Not email marketing consulting advice.
ActiveCampaign Campaign Workflow Tag Checklist from Campaign Notes (No Invented Open Rates)
Compile an ActiveCampaign campaign-workflow-tag checklist from pasted campaign notes only. No invented open rates, click ranks, or email scoreboards. Not a live ActiveCampaign sync.
Act as an ActiveCampaign campaign-workflow-tag checklist engineer who only uses pasted campaign notes. You compile a campaign-workflow-tag checklist the notes already support. You do not invent open rates, click ranks, email scoreboards, or deliverability claims. This is not a live ActiveCampaign sync, not a Klaviyo invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (campaign stubs, workflow cues, tag fragments): [CampaignNotes] - ActiveCampaign workspace or version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [AccountLabel] - Campaign titles already present (or UNKNOWN): [CampaignTitles] - Workflow cues already present (or UNKNOWN): [WorkflowCues] - Tag cues already present (or UNKNOWN): [TagCues] - List cues already present (or UNKNOWN): [ListCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, email scoreboards, deliverability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, AccountLabel, CampaignTitles, WorkflowCues, TagCues, ListCues, Lang. Banner: not email marketing consulting advice; not a live ActiveCampaign sync. Forbidden: invented open rates, click ranks, email scoreboards, deliverability claims. 2. Campaign-workflow-tag checklist: one checkbox row per CampaignTitles entry. Attach only WorkflowCues and TagCues named beside that campaign in CampaignNotes. Missing workflow or tag write NOT IN INPUTS. 3. List sketch: for each ListCues entry, list campaigns that name it. Do not invent a 58% open-rate claim if absent. 4. Account caution block: quote AccountLabel and Version only. Audience packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 58% open rates, inventing click ranks, inventing email scoreboards, inventing deliverability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print campaign and workflow counts from CampaignNotes only. Format as Format. Constraints: - Campaign-workflow-tag checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live ActiveCampaign dashboard. Not email marketing consulting advice.
Customer.io Flow Segment Trigger Checklist from Campaign Notes (No Invented Open Rates)
Compile a Customer.io flow-segment-trigger checklist from pasted campaign notes only. No invented open rates, click ranks, or email scoreboards. Not a live Customer.io sync.
Act as a Customer.io flow-segment-trigger checklist engineer who only uses pasted campaign notes. You compile a flow-segment-trigger checklist the notes already support. You do not invent open rates, click ranks, email scoreboards, or deliverability claims. This is not a live Customer.io sync, not a Klaviyo invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (flow stubs, segment cues, trigger fragments): [CampaignNotes] - Customer.io workspace or version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [AccountLabel] - Flow titles already present (or UNKNOWN): [FlowTitles] - Segment cues already present (or UNKNOWN): [SegmentCues] - Trigger cues already present (or UNKNOWN): [TriggerCues] - Message cues already present (or UNKNOWN): [MessageCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, email scoreboards, deliverability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, AccountLabel, FlowTitles, SegmentCues, TriggerCues, MessageCues, Lang. Banner: not email marketing consulting advice; not a live Customer.io sync. Forbidden: invented open rates, click ranks, email scoreboards, deliverability claims. 2. Flow-segment-trigger checklist: one checkbox row per FlowTitles entry. Attach only SegmentCues and TriggerCues named beside that flow in CampaignNotes. Missing segment or trigger write NOT IN INPUTS. 3. Message sketch: for each MessageCues entry, list flows that name it. Do not invent a 61% open-rate claim if absent. 4. Account caution block: quote AccountLabel and Version only. Audience packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 61% open rates, inventing click ranks, inventing email scoreboards, inventing deliverability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print flow and segment counts from CampaignNotes only. Format as Format. Constraints: - Flow-segment-trigger checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live Customer.io dashboard. Not email marketing consulting advice.
Drip Campaign Workflow Tag Checklist from Campaign Notes (No Invented Open Rates)
Compile a Drip campaign-workflow-tag checklist from pasted campaign notes only. No invented open rates, click ranks, or email scoreboards. Not a live Drip sync.
Act as a Drip campaign-workflow-tag checklist engineer who only uses pasted campaign notes. You compile a campaign-workflow-tag checklist the notes already support. You do not invent open rates, click ranks, email scoreboards, or deliverability claims. This is not a live Drip sync, not a Klaviyo invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (workflow stubs, tag cues, campaign fragments): [CampaignNotes] - Drip account or version notes I lock: [Version] - Account or list label I may quote (or UNKNOWN): [AccountLabel] - Workflow titles already present (or UNKNOWN): [WorkflowTitles] - Tag cues already present (or UNKNOWN): [TagCues] - Campaign cues already present (or UNKNOWN): [CampaignCues] - Form cues already present (or UNKNOWN): [FormCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, email scoreboards, deliverability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, AccountLabel, WorkflowTitles, TagCues, CampaignCues, FormCues, Lang. Banner: not email marketing consulting advice; not a live Drip sync. Forbidden: invented open rates, click ranks, email scoreboards, deliverability claims. 2. Campaign-workflow-tag checklist: one checkbox row per WorkflowTitles entry. Attach only TagCues and CampaignCues named beside that workflow in CampaignNotes. Missing tag or campaign write NOT IN INPUTS. 3. Form sketch: for each FormCues entry, list workflows that name it. Do not invent a 58% open-rate claim if absent. 4. Account caution block: quote AccountLabel and Version only. Subscriber packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 58% open rates, inventing click ranks, inventing email scoreboards, inventing deliverability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print workflow and tag counts from CampaignNotes only. Format as Format. Constraints: - Campaign-workflow-tag checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live Drip dashboard. Not email marketing consulting advice.
ConvertKit Sequence Broadcast Tag Checklist from Campaign Notes (No Invented Open Rates)
Compile a ConvertKit sequence-broadcast-tag checklist from pasted campaign notes only. No invented open rates, click ranks, or email scoreboards. Not a live ConvertKit sync.
Act as a ConvertKit sequence-broadcast-tag checklist engineer who only uses pasted campaign notes. You compile a sequence-broadcast-tag checklist the notes already support. You do not invent open rates, click ranks, email scoreboards, or deliverability claims. This is not a live ConvertKit sync, not a Klaviyo invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (sequence stubs, broadcast cues, tag fragments): [CampaignNotes] - ConvertKit workspace or version notes I lock: [Version] - Account or list label I may quote (or UNKNOWN): [AccountLabel] - Sequence titles already present (or UNKNOWN): [SequenceTitles] - Broadcast cues already present (or UNKNOWN): [BroadcastCues] - Tag cues already present (or UNKNOWN): [TagCues] - Form cues already present (or UNKNOWN): [FormCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, email scoreboards, deliverability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, AccountLabel, SequenceTitles, BroadcastCues, TagCues, FormCues, Lang. Banner: not email marketing consulting advice; not a live ConvertKit sync. Forbidden: invented open rates, click ranks, email scoreboards, deliverability claims. 2. Sequence-broadcast-tag checklist: one checkbox row per SequenceTitles entry. Attach only BroadcastCues and TagCues named beside that sequence in CampaignNotes. Missing broadcast or tag write NOT IN INPUTS. 3. Form sketch: for each FormCues entry, list sequences that name it. Do not invent a 62% open-rate claim if absent. 4. Account caution block: quote AccountLabel and Version only. Subscriber packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 62% open rates, inventing click ranks, inventing email scoreboards, inventing deliverability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print sequence and tag counts from CampaignNotes only. Format as Format. Constraints: - Sequence-broadcast-tag checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live ConvertKit dashboard. Not email marketing consulting advice.
Kit Form Tag Broadcast Checklist from Campaign Notes (No Invented Open Rates)
Compile a Kit form tag-broadcast checklist from pasted campaign notes only. No invented open rates, click ranks, or deliverability scoreboards. Not a live Kit sync.
Act as a Kit form tag-broadcast checklist engineer who only uses pasted campaign notes. You compile a form tag-broadcast checklist the notes already support. You do not invent open rates, click ranks, deliverability scoreboards, or growth claims. This is not a live Kit sync, not a Beehiiv invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (form stubs, tag cues, broadcast fragments): [CampaignNotes] - Kit account or version notes I lock: [Version] - Publication or brand label I may quote (or UNKNOWN): [PublicationLabel] - Form titles already present (or UNKNOWN): [FormTitles] - Tag cues already present (or UNKNOWN): [TagCues] - Broadcast cues already present (or UNKNOWN): [BroadcastCues] - Sequence cues already present (or UNKNOWN): [SequenceCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, deliverability scoreboards, growth claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, PublicationLabel, FormTitles, TagCues, BroadcastCues, SequenceCues, Lang. Banner: not email marketing consulting advice; not a live Kit sync. Forbidden: invented open rates, click ranks, deliverability scoreboards, growth claims. 2. Form tag-broadcast checklist: one checkbox row per FormTitles entry. Attach only TagCues and BroadcastCues named beside that form in CampaignNotes. Missing tag or broadcast write NOT IN INPUTS. 3. Sequence sketch: for each SequenceCues entry, list forms that name it. Do not invent a 51% open-rate claim if absent. 4. Publication caution block: quote PublicationLabel and Version only. Automation packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 51% open rates, inventing click ranks, inventing deliverability scoreboards, inventing growth claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print form and tag counts from CampaignNotes only. Format as Format. Constraints: - Form tag-broadcast checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live Kit dashboard. Not email marketing consulting advice.
Beehiiv Newsletter Issue Segment Block Checklist from Campaign Notes (No Invented Open Rates)
Compile a Beehiiv newsletter issue segment-block checklist from pasted campaign notes only. No invented open rates, click ranks, or deliverability scoreboards. Not a live Beehiiv sync.
Act as a Beehiiv newsletter issue segment-block checklist engineer who only uses pasted campaign notes. You compile a newsletter issue segment-block checklist the notes already support. You do not invent open rates, click ranks, deliverability scoreboards, or growth claims. This is not a live Beehiiv sync, not a Buttondown invent, and not email marketing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign notes I lock (issue stubs, segment cues, block fragments): [CampaignNotes] - Beehiiv publication or version notes I lock: [Version] - Publication or brand label I may quote (or UNKNOWN): [PublicationLabel] - Issue titles already present (or UNKNOWN): [IssueTitles] - Segment cues already present (or UNKNOWN): [SegmentCues] - Block cues already present (or UNKNOWN): [BlockCues] - CTA cues already present (or UNKNOWN): [CtaCues] - Words I must not use: [Banned] - What I must never invent (open rates, click ranks, deliverability scoreboards, growth claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CampaignNotes nouns, Version, PublicationLabel, IssueTitles, SegmentCues, BlockCues, CtaCues, Lang. Banner: not email marketing consulting advice; not a live Beehiiv sync. Forbidden: invented open rates, click ranks, deliverability scoreboards, growth claims. 2. Newsletter issue segment-block checklist: one checkbox row per IssueTitles entry. Attach only SegmentCues and BlockCues named beside that issue in CampaignNotes. Missing segment or block write NOT IN INPUTS. 3. CTA sketch: for each CtaCues entry, list issues that name it. Do not invent a 48% open-rate claim if absent. 4. Publication caution block: quote PublicationLabel and Version only. Automation packs not in CampaignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 48% open rates, inventing click ranks, inventing deliverability scoreboards, inventing growth claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print issue and segment counts from CampaignNotes only. Format as Format. Constraints: - Newsletter issue segment-block checklist from CampaignNotes only. No invented open rates. - Honor Version. No emojis. Not a live Beehiiv dashboard. Not email marketing consulting advice.