Marketing
248 prompts in this category · Page 3 of 21
Google Merchant Center Product Feed Attribute Repair Planner: GTIN MPN Brand Rules, Image Requirements, Shipping Attributes, and a Supplemental Feed Patch Sheet
Turn Merchant Center product feed rejections into a repair plan: fix GTIN, MPN, and brand identity rules, image policy failures, shipping and return attributes, then produce a supplemental feed patch sheet merchandisers can upload without guessing column names.
Act as a Google Merchant Center feed specialist who clears product attribute rejections, enforces GTIN MPN brand identity rules, fixes image and shipping attributes, and writes supplemental feed patches sellers can upload. Inputs: - Store platform and how the primary feed is generated (Shopify app, Content API, CSV scheduled fetch): [FeedSource] - Sample rejected offer rows with item id, title, brand, GTIN, MPN, image link, and the Merchant Center issue codes: [RejectedOffers] - Shipping model (table rates, carrier calculated, free over threshold) and return policy URL if any: [ShippingAndReturns] - Whether products are apparel, media, or hard goods that change identifier rules: [ProductVertical] - Countries and languages in the feed: [TargetMarkets] - Output format: [Format] Generate: 1. An issue triage table: each RejectedOffers row mapped to root cause (identifier, image, shipping, price mismatch) with a one line fix. 2. A GTIN MPN brand rule card for ProductVertical: when GTIN is required, when MPN plus brand substitutes, and when identifier exists false is allowed. 3. An image fix list: main image rules (no promo overlay, correct URL, enough pixels) tied to each failing offer; mark uncertain policy edges as [confirm Merchant Center image specs]. 4. A shipping attributes block for ShippingAndReturns and TargetMarkets: shipping(country:price) or account level shipping services, plus return policy link attribute if required. 5. A supplemental feed patch sheet: column headers Google expects, one corrected row per RejectedOffers item, and which fields override the primary feed. 6. A revalidation checklist: upload patch, request review timing, and which issues need a primary feed fix instead of supplemental. 7. A prevention note for FeedSource: which platform field maps to each Google attribute so the next sync does not reintroduce bad GTINs. 8. A FAQ for common false fixes (fake GTINs, white background myths, deleting offers instead of patching). Constraints: - Do not invent GTIN check digit math results or claim a specific review SLA; use [confirm]. - Never recommend fabricating GTINs. Plain operator tone. No em dashes.
Shopify Product Metafields Filter Pack Builder: Definition Namespace, List vs Single Line Types, Collection Filter Facets, Storefront Theme Hooks, and A CSV Import Map
Turn a product catalog brief into a Shopify metafield definition pack sellers can paste into Settings: namespaces and keys, type choices that power collection filters, theme liquid or Hydrogen hooks, validation rules, and a CSV column map so filter facets stay consistent across SKUs.
Act as a Shopify catalog architect who designs product metafield definitions that power Online Store collection filters, keeps namespaces clean across migrations, and maps CSV imports so every SKU gets the same facet values. Inputs: - Store plan and storefront stack (Online Store 2.0 theme name, Hydrogen, or headless): [StorefrontStack] - Product types and the filter facets buyers must use (material, fit, scent family, wattage, age range, or similar): [FilterFacets] - Existing metafield namespaces and keys already in Settings > Custom data (paste names if any): [ExistingDefinitions] - Sample product rows with the raw attribute values you want stored: [SampleProducts] - Who edits values day to day (merchant admin, matrixify CSV, ERP sync): [EditorsAndImport] - Output format: [Format] Generate: 1. A namespace and key plan: one product metafield definition per facet in FilterFacets, with a short human name, namespace.key, description for staff, and whether it is product or variant level. 2. A type table: for each facet choose single line text, list of single line text, integer, decimal, true/false, color, or metaobject reference; say why that type unlocks the Online Store filter or Hydrogen filter you need. 3. Validation rules: allowed values list, min/max for numbers, required vs optional, and a note when a metaobject is better than free text. 4. A conflict check against ExistingDefinitions: rename, reuse, or deprecate, never invent a second key for the same meaning. 5. Theme or Hydrogen hooks from StorefrontStack: which section settings or liquid filters expose each metafield, and what to mark as "confirm in theme editor" if the theme version is unclear. 6. A CSV import map from EditorsAndImport: column header, metafield namespace.key, value format examples, and how multi value lists are delimited. 7. A sample filled row for each SampleProducts product showing the exact values after cleanup (normalize casing and synonyms). 8. A go live checklist: create definitions, backfill via CSV, enable each facet on the collection filter, spot check one collection on mobile. Constraints: - Do not invent Shopify plan limits, app names, or API version numbers; use [check Shopify docs] gaps. - Prefer list of single line text for multi select filters buyers combine. - Plain operator tone. No em dashes.
Nonprofit Year End Fundraising Appeal Builder: Donor Segments (Current, LYBUNT, SYBUNT, Lapsed), Ask Strings from Last Gift, Print Letter and Reply Device, December Email Series, Matching Gift Deadline, and IRS Acknowledgment Language
Build a nonprofit's year end appeal from the donor file: segments with their own message, ask strings calculated from each donor's most recent or largest gift, a one page letter and reply device, a short December email series, honest matching gift language, and gift acknowledgment wording that meets the written acknowledgment rule for gifts of $250 or more.
Act as a nonprofit development director who runs year end appeals for small and mid sized charities, segments the donor file before writing a word, and writes to one reader about one result. Inputs: - Organization, mission in one sentence, and one specific story or result from this year with permission to share: [ImpactStory] - Donor file summary: counts and typical gifts for current year donors, LYBUNT (gave last year but not this year), SYBUNT (gave some earlier year), lapsed, and new prospects: [DonorSegments] - Goal amount, match details if any (who, cap, deadline, terms), and campaign dates: [GoalAndMatch] - Channels and budget: print mail volume, email list size, send tool: [Channels] - Gift options: online form link, check address, monthly giving, DAF and stock gifts: [GiftOptions] - Output format: [Format] Generate: 1. Segment plan: one row per segment in DonorSegments with the message angle (thank and upgrade for current donors, "we missed you this year" for LYBUNT, renewal for SYBUNT and lapsed, introduction for prospects), channel, and whether they get print. 2. Ask string rules: base the first ask on most recent gift (or highest previous gift for major donors), then roughly 1x, 1.5x, and 2x rounded to clean numbers, plus Other. Show the math for three sample donors and a default string for donors with no history. 3. Print letter of one page from ImpactStory: open with one person or moment, state the need, make one clear ask with the donor's first ask amount, mention the match only as GoalAndMatch states it, and add a P.S. with the deadline. 4. Reply device copy: name and address block, the personalized ask string, monthly giving checkbox, gift options from GiftOptions, and the note that mailed gifts count for the tax year when postmarked by December 31. 5. December email series: about five sends from Giving Tuesday to December 31, each with subject, preview text, one paragraph, and one button, ending with two short sends on December 30 and 31. 6. Match language that is exactly true: name the matcher, the cap, and what happens to gifts after the cap. If there is no match, use none. 7. Acknowledgment template: thank you within 48 hours, gift amount and date, and for gifts of $250 or more a statement of whether any goods or services were provided in return. 8. A results sheet: response rate, average gift, and dollars by segment, plus the date to pull LYBUNT donors for a January follow up. Constraints: - No invented statistics or beneficiaries; use [add result] gaps. - Warm, plain, second person. No guilt language, no em dashes.
Affiliate Program Terms Builder for Impact, PartnerStack, or ShareASale: Commission Tiers, Referral Window, Locking Period, Reversal Rules, Brand Bidding and Coupon Site Policy, FTC Disclosures, and a Partner Welcome Kit
Write the program terms a brand loads into its affiliate network before recruiting partners: commission tiers that fit your margin, a referral window and attribution rule, a locking period that covers your refund window, reversal reasons, clear rules on trademark bidding, coupon and deal sites, incentivized traffic and self referrals, FTC disclosure requirements, and a short welcome kit for approved partners.
Act as an affiliate program manager who has launched partner programs on Impact, PartnerStack, and ShareASale, and has watched a program lose money because coupon sites took credit for sales the brand would have made anyway. Inputs: - Product, price points, gross margin, and refund window: [ProductEconomics] - Network or platform you will run on, and whether you sell one time or by subscription: [Network] - Partner types you want (content sites, creators, newsletters, coupon sites, software partners, agencies): [PartnerMix] - Paid search setup and trademarked terms you bid on: [BrandTerms] - Channels or tactics you already know you do not want: [Prohibited] - Output format: [Format] Generate: 1. Commission math from ProductEconomics: the highest payout the margin allows after refunds and network fees, then a base rate and up to two performance tiers (by monthly sales or revenue). For subscriptions on Network, choose between a one time bounty, a first year recurring percentage, or a capped recurring term, and show the cost per new customer for each. 2. Attribution rules: referral window length (state it in days), last click or first click, what happens when two partners touch the same order, and whether coupon codes override cookies. Explain the trade off in one line each. 3. A locking period at least as long as the refund window, plus the reversal reasons: refunds, chargebacks, fraud, duplicate orders, orders by the partner or their household, and orders placed in breach of these terms. 4. Brand bidding policy from BrandTerms: no bidding on trademarked terms or misspellings, no use of the brand in ad copy or display URLs, negative keyword request, and how violations are handled (warning, reversal, removal). 5. Coupon and deal site policy for PartnerMix: only codes issued to that partner, no publishing of codes issued to others, a lower rate or exclusion for coupon placements if the margin needs it, and a list of what counts as a valid deal. 6. Prohibited traffic from Prohibited plus standard bans: incentivized clicks, cookie stuffing, toolbar or browser extension injection, adware, spam email, and posing as the brand. 7. FTC disclosure section: a clear and conspicuous disclosure close to the link or claim, on the screen or in the audio for video, not hidden behind a "more" link or only in a bio, plus three sample disclosures by format. Mark "check the current FTC Endorsement Guides" rather than quoting the rule. 8. Payment terms: minimum payout, payment schedule after locking, and tax form collection handled through the network. 9. A partner welcome kit under 250 words: what to promote, approved claims, brand assets location, disclosure reminder, and a contact. Constraints: - Do not promise earnings or invent conversion rates; every rate must trace to ProductEconomics. - Use the network's own field names only when you are sure; otherwise say "map to your network's setting". No em dashes.
Sweepstakes and Giveaway Official Rules Writer for US Brands: Consideration Check, No Purchase Necessary and Free Entry Method, Entry Period with Time Zone, ARV and Odds Language, NY and FL Registration Triggers, and Platform Release
Write official rules for a US sweepstakes or social giveaway: check prize, chance, and consideration so it stays a legal promotion, state no purchase necessary with an equal free entry method, set eligibility and an entry period with a time zone, describe prizes with approximate retail value and odds language, flag New York and Florida registration triggers, add the platform release, and plan winner notice, affidavits, and tax forms.
Act as a promotions manager at a US consumer brand who drafts sweepstakes and giveaway official rules for legal review, runs entries and winner verification, and has seen a giveaway pulled because the rules were missing or entry required a purchase. Inputs: - Promotion concept, sponsor legal name and address, and where it runs (Instagram, website, in store, email): [PromotionBrief] - Prizes: description, quantity, approximate retail value (ARV) of each, and any conditions: [Prizes] - Entry methods and limits, including anything that costs the entrant money or effort: [EntryMethods] - Dates and times for start and end, and the time zone: [EntryPeriod] - Eligibility you want (age, residency, exclusions for employees): [Eligibility] - Output format: [Format] Generate: 1. A legal structure check: a lottery has prize, chance, and consideration, so a sweepstakes removes consideration. Review EntryMethods for anything that counts as consideration (a purchase, a paid membership, significant effort) and give a free alternate method of entry with equal chance and an equal entry limit. 2. Official rules sections in order: NO PURCHASE NECESSARY statement with "a purchase will not increase your chances of winning"; void where prohibited; eligibility; sponsor; entry period with exact start and end dates, times, and time zone; how to enter for each method; entry limits; winner selection by random drawing with date and who conducts it; odds depend on the number of eligible entries received; prize description with ARV and total ARV; winner notification and response deadline with an alternate winner rule; affidavit of eligibility and liability and publicity release where allowed by law; taxes are the winner's responsibility; general conditions; limitation of liability; privacy; disputes and governing law; winner list request address. 3. A platform release for social promotions: for Instagram and Facebook, state that the promotion is not sponsored, endorsed, administered by, or associated with Instagram or Meta, and that entrants release the platform. Note that tagging people in content they are not in breaks Instagram promotion guidelines. 4. State registration triggers: if total ARV of all prizes is over 5,000 US dollars, New York and Florida require registration and bonding before launch, with lead times to confirm with counsel. State whether Prizes crosses this line. 5. Tax and paperwork: an IRS Form 1099 MISC is issued for prizes valued at 600 US dollars or more, so collect a W 9 from the winner before shipping. 6. A short rules summary for the post caption or landing page: no purchase necessary, eligibility, dates, how to enter, prize and ARV, and a link to the full rules. 7. A winner process checklist: draw record, eligibility check, notice, response window, affidavit, alternate draw, prize fulfillment, winners list. Constraints: - This is a draft for legal review, not legal advice. Do not promise compliance for every state. - Never invent prize values, sponsor details, or dates. No em dashes.
Co-op Advertising and MDF Claim Packet Builder for Dealers: Program Guide Eligibility, Accrual Balance Math, Prior Approval Check, Proof of Performance by Media Type, Brand Compliance Review, and a Claim Deadline Tracker
Get manufacturer co-op and market development fund money paid instead of rejected: check each ad against the program guide, compute the available accrual and the reimbursable amount, confirm prior approval, assemble the right proof of performance for print, radio, digital, and mail, run a logo and disclaimer review, and track every claim deadline.
Act as a channel marketing coordinator who files co-op advertising and MDF claims for independent dealers, has read dozens of manufacturer program guides, and has watched claims bounce for a missing tearsheet date, a competitor logo in the same ad, a radio spot with no affidavit, and a claim filed one day past the window. Inputs: - Program guide rules: accrual rate, eligible purchases, reimbursement share, eligible media, prior approval rule, claim window, and required documents: [ProgramGuide] - Eligible purchase total for the period and claims already paid: [AccrualData] - Each ad or activity: media type, dates, cost, vendor, and products shown: [Activities] - Proof you already have for each activity (tearsheets, screenshots, invoices, affidavits): [ProofOnHand] - Brand rules: logo use, required disclaimers, competitor product rules: [BrandRules] - Claim portal or form the manufacturer uses: [ClaimPortal] - Output format: [Format] Generate: 1. An eligibility check per activity against ProgramGuide: eligible media, eligible products, dates inside the program period, and whether prior approval was required and obtained. 2. Accrual math from AccrualData: eligible purchases times the accrual rate, minus claims already paid, equals the balance available. Show every line. 3. Reimbursement math per activity: eligible cost times the reimbursement share, then capped by the remaining balance. Exclude agency fees, design time, or shipping when the guide says so, and show what was excluded. 4. A proof of performance list by media type using only what ProgramGuide asks for, typically: print needs a full page tearsheet showing the publication name and run date; radio and TV need the script and a station affidavit of performance with air dates and times; digital needs dated screenshots and the platform invoice or billing report; direct mail needs the piece and the postal or printer receipt. 5. A gap table comparing the required proof with ProofOnHand, with who to ask for each missing item. 6. A brand compliance review per ad against BrandRules: approved logo version, required trademark or financing disclaimers, and competitor products sharing the ad. 7. ClaimPortal field entries: activity, dates, gross cost, claimed amount, and the file list in upload order with clear file names. 8. A deadline tracker: claim window close date per activity, a submit-by date one week earlier, and a follow-up date if no payment arrives. Constraints: - Never invent accrual rates, shares, or deadlines. If ProgramGuide does not state one, write "confirm with the program administrator". - No em dashes.
Google Ads Offline Conversion Import Planner for Lead Gen: GCLID Capture in Hidden Fields, CRM Stage to Conversion Action Mapping, Upload CSV Headers and Time Zone, 90 Day Window, Primary vs Secondary Goals, and Error Fixes
Feed real sales outcomes back into Google Ads: capture the GCLID on every form, store it in the CRM, map lead stages to import conversion actions, build an upload file with the right headers, time zone, and values, respect the click window, choose which actions are primary for bidding, and fix the usual upload errors.
Act as a paid search analyst who sets up Google Ads offline conversion imports for service businesses with long sales cycles, and who has fixed uploads rejected for missing click IDs, conversion times before the click, and conversion names with a stray space. Inputs: - Business and sales process: what a lead is, the CRM stages a lead passes through, and typical time from lead to sale: [SalesProcess] - CRM or lead store and how forms reach it (website form tool, call tracking, chat): [LeadStack] - Current Google Ads conversion actions, which are primary, and the bid strategy in use: [CurrentConversions] - Values you can stand behind per stage (average contract value, or a value only at close): [StageValues] - Account time zone and the time zone the CRM stores timestamps in: [TimeZones] - Consent setup for ad user data where required, and who owns the upload: [ConsentAndOwner] - Output format: [Format] Generate: 1. A GCLID capture plan from LeadStack: auto tagging on, a hidden form field that stores gclid from the landing URL (and gbraid or wbraid if present), persistence across pages, and a CRM field to hold it. Mark CHECK for any tool specific step. 2. A stage to conversion action map: one import conversion action per CRM stage worth optimizing, with exact names, count setting (one per lead), value from StageValues, and click through window. 3. Primary vs secondary: which action bidding should use given CurrentConversions and how many conversions per month each stage produces, and which stay secondary for reporting so nothing is double counted. 4. The upload file: a Parameters:TimeZone line from TimeZones, then the headers Google Click ID, Conversion Name, Conversion Time, Conversion Value, Conversion Currency, with three sample rows and the time format. 5. Timing rules: conversion time must be after the click, clicks older than the action's window will be rejected, and how often to upload (scheduled file, Sheets, or API). 6. A fallback for leads with no click ID: enhanced conversions for leads with hashed email, and where consent from ConsentAndOwner limits it. 7. An upload error table: common errors, what causes each, and the fix. 8. A first month QA plan: compare CRM counts to imported counts by week and flag gaps over a set threshold. Constraints: - Use only facts from Inputs. Never promise lower cost per lead or quote typical lift. Mark UI paths that may have moved as CHECK. - Plain language for the business owner; no em dashes.
Google Ads Performance Max Asset Group Builder: Themed Asset Groups, Audience Signals, Search Themes, Headlines and Descriptions to Character Limits, Image and Video Specs, Listing Groups, Brand Exclusions, and Final URL Expansion
Plan a Performance Max campaign asset group by asset group: one theme per group, audience signals from your own data, search themes, headlines, long headlines, and descriptions written to character limits and counted, image and video asset specs, Merchant Center listing groups, brand exclusions, and a reasoned on or off decision for final URL expansion.
Act as a paid search manager who builds and audits Google Ads Performance Max campaigns for ecommerce and lead generation advertisers, and who treats asset groups as themed mini campaigns rather than one big bucket of every product. Inputs: - Business and goal: ecommerce with a Merchant Center feed or lead generation, conversion action, target CPA or ROAS if set: [CampaignGoal] - Product lines or services to group, with landing page URLs and margin notes: [ProductThemes] - First party data available: customer lists, website visitors, app users, past converters: [AudienceData] - Keywords and queries that already convert in Search campaigns: [SearchTerms] - Brand rules: competitor names to avoid, own brand traffic handled by a brand Search campaign or not, claims legal has approved: [BrandRules] - Creative on hand: images with sizes, logos, videos with lengths: [CreativeInventory] - Pages that must never receive traffic (careers, blog, support, out of stock categories): [UrlExclusions] - Output format: [Format] Generate: 1. An asset group map: one group per theme from ProductThemes, each with its final URL, why it is separate, and the listing group filter (brand, product type, custom label) when a feed is attached. 2. Audience signals per group from AudienceData: customer list, custom segments built from SearchTerms and competitor style URLs, and interests. Note that signals guide the start and are not hard targeting. 3. Search themes per group, drawn from SearchTerms, kept within the current limit shown in the interface, marked CHECK. 4. Text assets per group: up to 15 headlines of 30 characters or fewer, up to 5 long headlines of 90 or fewer, up to 5 descriptions of 90 or fewer with one short description of 60 or fewer, and a business name. Show the character count after each line and vary angles: product, benefit, proof, offer, brand. 5. Image and video asset plan from CreativeInventory: landscape 1.91:1, square 1:1, and portrait 4:5 images, a logo, and at least one real video so the system does not auto generate one. List gaps to shoot. 6. Brand exclusions and negative coverage from BrandRules: a brand list to exclude when brand Search is separate, and account level negative keywords for terms you never want. 7. A final URL expansion decision: on or off with the reason, plus URL exclusion rules from UrlExclusions if on. 8. A launch checklist and a first 30 days review plan: asset ratings, search term insights, listing group performance, and what to change only after enough conversions. Constraints: - Never invent performance numbers or benchmarks. Use only claims in BrandRules. - Asset limits change; tell the user to confirm counts and sizes in Google Ads Help. No em dashes, no all caps headlines.
Google Local Services Ads Profile and Lead Management Planner for Home Services: Job Types and Service Area Setup, Weekly Budget, Business Hours, Reviews, Lead Handling Scripts, and Lead Credit Requests with Evidence
Set up and run Google Local Services Ads for a plumber, HVAC company, electrician, roofer, or other home services business: profile readiness checks, job types and service area matched to work you will actually take, a weekly budget you control, honest business hours, a review request routine, scripts for calls, messages, and bookings, and lead credit requests backed by evidence notes.
Act as a home services marketing manager who runs Google Local Services Ads accounts for plumbing, HVAC, electrical, and roofing companies, and who judges the account by booked jobs from the lead log, not by how many times the phone rang. Inputs: - Business profile: trade, license and insurance status, verification or screening status shown in the account, years in business: [BusinessProfile] - Job types you do, job types you do not do, and jobs you want more of: [JobTypes] - Service area: cities or ZIP codes, how far techs will drive, areas you want to avoid: [ServiceArea] - Weekly budget the owner is willing to spend and average ticket or job value by job type: [WeeklyBudget] - Business hours and who actually answers the phone in each window, including after hours: [Hours] - Review count and rating on the profile and how you currently ask customers for reviews: [Reviews] - Recent leads exported from the account: date, lead type (call, message, booking), job type, location, outcome, call notes: [LeadLog] - Output format: [Format] Generate: 1. A profile readiness checklist from BusinessProfile: verification status, license and insurance documents, business name and address match, and anything the account shows as pending, marked CHECK where Inputs do not confirm it. 2. A job types map: which job types to turn on, which to turn off because they produce leads you cannot book, and which to watch, with a reason tied to JobTypes or LeadLog. 3. A service area plan: ZIP codes or cities kept, removed, or added, based on drive time, where booked jobs came from in LeadLog, and areas the owner wants to avoid. 4. Budget guidance: set the weekly budget at the owner's number, then show how to judge it with the owner's own figures: lead cost from the account's reports, booking rate from LeadLog, and job value from WeeklyBudget. Leave any cost per lead blank until it comes from the account. 5. Business hours: set hours only for times someone answers live, and a plan for after hours calls and messages if Hours shows a gap. 6. A review routine: when and how to send the review request link from the account after a finished job, who sends it, and a short message. No incentives for reviews and no review gating. 7. Lead handling scripts: a phone answer script that qualifies job type, location, and urgency in under a minute; a message lead reply; a booking confirmation; and a rule to update each lead's status in the account the same day. 8. Lead credit requests: for each LeadLog entry that looks invalid, the likely reason (outside service area, job type not offered, spam or solicitation, wrong number, repeat contact), the evidence to note (call recording time stamp, location stated, what was asked), and the request text. Match reasons to the current options in the account, marked CHECK. 9. A weekly 20 minute review checklist: leads by outcome, credits requested and returned, job types and areas to adjust. Constraints: - Do not invent cost per lead, ranking factors, or approval times. Use only numbers from Inputs or the account. - Do not request credit for a real customer who simply did not book; that is a sales issue, not an invalid lead. - Policy and credit options change by country and trade; tell the user to confirm in the account. No em dashes.
Google Merchant Center Disapproval Fixer: Item Issues Triage, Price and Availability Mismatches, Missing Identifiers, Image Policy Problems, Supplemental Feed Fixes, and When to Request a Review
Clear the Needs attention list in Google Merchant Center for an online store: sort item issues from account issues, trace each price, availability, GTIN, and image problem back to the source feed or product page, write supplemental feed or rule fixes when the source cannot change, and decide what needs a review request.
Act as a Google Shopping feed specialist who manages Merchant Center accounts for Shopify, WooCommerce, and BigCommerce stores, and who fixes disapprovals at the source instead of patching the same products every week. Inputs: - The issue list from Merchant Center, with each issue name, attribute, and number of affected products: [IssueList] - Sample rows for affected products: id, title, price, sale_price, availability, gtin, mpn, brand, link, image_link: [SampleItems] - What the product page shows for the same items (price, sale price, stock message, structured data if known): [LandingPageFacts] - How products get into Merchant Center (Shopify Google and YouTube app, WooCommerce plugin, scheduled file, API): [FeedSource] - Any account level warnings or suspension notices: [AccountStatus] - Target countries and currency: [Countries] - Output format: [Format] Generate: 1. A triage table: each issue from IssueList, whether it is item level or account level, data quality or policy, products affected, and priority by lost impressions (disapproved first, then limited, then warnings). 2. Price mismatch diagnosis: compare SampleItems with LandingPageFacts for price, sale_price, sale_price_effective_date, currency, and tax handling for the country. Point to the usual causes: a sale that ended on the site but not in the feed, a variant price, a cached page, or schema.org Offer markup that disagrees with the visible price. 3. Availability mismatch diagnosis: map the store's stock states to in_stock, out_of_stock, preorder, or backorder, with availability_date where required, and find where the sync lags. 4. Identifier fixes: which products need a manufacturer gtin, which can use brand plus mpn, and which are custom or handmade and qualify for identifier_exists set to no. Never generate or guess a GTIN. 5. Image fixes: promotional overlays, watermarks, text, borders, or placeholder images; say what a compliant image looks like and whether a separate image_link or additional_image_link solves it. 6. Source fixes per FeedSource first, then a supplemental feed or feed rule for anything the source cannot express, with example rows. 7. A review plan: which items will be rechecked automatically after the fix, which need a manual review request, and for account level issues the checks to finish (contact details, returns policy, secure checkout, accurate business info) before requesting one, because repeated requests can add a waiting period. Constraints: - Do not promise reapproval times or claim to know Google's internal review; quote issue names exactly as given. - Do not suggest hiding products from the feed to clear an account level warning or masking prices. - Mark anything you cannot confirm from Inputs as CHECK. No em dashes.
App Store Custom Product Page Planner: Audience Specific Screenshot Sets, App Preview Order, Promotional Text, Deep Links, Apple Search Ads Ad Group Mapping, and a Read Out Plan
Plan App Store custom product pages for an iOS app so each ad audience lands on a page that matches why they tapped: an audience to page map, a screenshot story for each page frame by frame, app preview order, promotional text within the 170 character limit, deep link targets, Apple Search Ads ad group and keyword theme mapping, and a plan for reading results in App Analytics.
Act as an app store optimization specialist who builds App Store custom product pages for subscription iOS apps and ties each page to a paid traffic source, so the screenshots someone sees match the ad or keyword that brought them in. Inputs: - App name, category, and the default product page's current first three screenshots: [AppBasics] - Distinct audiences or use cases you buy traffic for: [Audiences] - Features and screens you can show for real today (no roadmap features): [ShippedFeatures] - Traffic sources per audience (Apple Search Ads keyword themes, social ads, creator links, email): [TrafficSources] - In app destinations you can deep link to: [DeepLinkTargets] - Localizations you support: [Localizations] - Output format: [Format] Generate: 1. An audience to page map: one custom product page per audience in Audiences, the promise the page makes, and the TrafficSources that will point to it. Merge audiences whose screenshots would be nearly identical. 2. A screenshot story for each page: frame 1 to frame 6 with the screen from ShippedFeatures and a short caption idea for each. Frames 1 to 3 must carry the promise because many people never swipe past them. 3. App preview order: which preview leads on each page and the first three seconds it should show. 4. Promotional text for each page and each item in Localizations, at or under 170 characters, counted. 5. A deep link for each page from DeepLinkTargets so people who already have the app open the matching screen. 6. Apple Search Ads mapping: for each page, the ad group, keyword themes, and the ad variation that uses the page. Keep brand keywords on the default page. 7. A read out plan in App Analytics: compare each page's conversion rate to the default page for the same source and period, set the minimum run time before judging, and list what to change next if a page underperforms. Constraints: - Every page goes through App Review. Show only shipped features and no pricing claims that change by region. - Do not confuse custom product pages with product page optimization tests of the default page; mention the difference once. - Do not invent ratings, download counts, awards, or conversion rates. No em dashes.
USPS Every Door Direct Mail Campaign Planner: Carrier Route Selection, Flat Size Postcard Specs, Indicia, Bundling, and a Trackable Offer for a Local Business
Plan a USPS Every Door Direct Mail campaign for a local service business: choose carrier routes from the EDDM mapping tool by household type and distance, size the mailpiece so it qualifies as a flat, lay out both sides with the right indicia and postal customer line, plan bundles and facing slips for drop off, and attach a dedicated phone number or code so responses can be counted.
Act as a direct mail marketing coordinator who runs USPS Every Door Direct Mail campaigns for home service and retail businesses and has had mailings refused at the counter for wrong sizes and missing facing slips. Inputs: - Business, service area, and address of the Post Office or BMEU where the mail will be dropped: [BusinessArea] - Ideal customer (homeowners, renters, households with kids, businesses) and any ZIP Codes to include or avoid: [TargetHouseholds] - Route data copied from the EDDM online tool: route IDs, residential and business counts, age and income ranges if shown: [RouteData] - Budget for print plus postage and the target number of pieces: [Budget] - Offer, deadline, and how responses will be tracked (unique number, promo code, QR to a landing page): [OfferTracking] - Mailing type (EDDM Retail at the counter or EDDM BMEU with a mailing permit) and printer, if chosen: [MailingType] - Output format: [Format] Generate: 1. Route selection: rank the routes in RouteData against TargetHouseholds and pick a set that fits Budget. Note that EDDM delivers to every address on a chosen route, and use residential only when businesses are not wanted. Show the piece count per route and the total. 2. Mailpiece spec that qualifies as an EDDM flat: at least one of length over 10.5 inches, height over 6.125 inches, or thickness over 0.25 inch, within the maximum flat size, with a recommended trim size, stock, and bleed for the printer. Mark exact limits as VERIFY against the current USPS Business Mail 101 page. 3. Address side layout: indicia block for MailingType (Retail EDDM or the permit imprint wording), the ECRWSS postal customer line, return address, and a clear zone. No personal names or full addresses on EDDM pieces. 4. Front and back copy: one headline, three proof points the business can back up, the offer with the deadline, one call to action, and the tracking element from OfferTracking. 5. Bundling and drop off checklist: bundle sizes, facing slips per bundle with route ID and count, the PS Form required for MailingType, payment, and the drop window before the in-home target. 6. Response tracking sheet: columns for route, date, channel, and booked jobs, plus how to compare cost per response across routes after the deadline. Constraints: - Do not invent postage rates, route counts, or response rates. Use RouteData and Budget only and leave unknown prices as [rate]. - Do not promise delivery dates. No em dashes.