What can I ask Grady?
A lot. The examples below are organized around the marketing lifecycle — from setting strategy through to analyzing results. The goal is to spark ideas based on where you are right now, not to prescribe a fixed workflow. You don’t need to use these word-for-word. Describe what you need in plain language and Grady will work out the steps. These are starting points.01 — Strategy
02 — Planning
03 — Creative
04 — Assets (DAM)
05 — Channel Orchestration
06 — Authoring
07 — Review & QA
08 — Launch
09 — Analyze & Optimize
- 01 Strategy
- 02 Planning
- 03 Creative
- 04 Assets (DAM)
- 05 Channel Orchestration
- 06 Authoring
- 07 Review & QA
- 08 Launch
- 09 Analyze & Optimize
1.01 — Plan a product launch campaign across web, email, and social
1.01 — Plan a product launch campaign across web, email, and social
Plan a launch campaign for [product name] across web, email, and social. Target launch date: [date]. Include: a messaging framework, channel-by-channel asset list, go-live timeline, and a task breakdown I can execute in Gradial.
1.02 — Build a Q3 content calendar across all channels
1.02 — Build a Q3 content calendar across all channels
Build a Q3 content calendar for [team / brand]. Include web pages, emails, and social posts mapped to our campaign themes: [theme 1], [theme 2], [theme 3]. Align to key dates: [list of dates or events]. Format it so I can use it to kick off tasks in Gradial.
1.03 — Take last year's best-performing campaign and adapt it for this year
1.03 — Take last year's best-performing campaign and adapt it for this year
Take our [campaign name] campaign from [year] and adapt it for [this year / new product / new market]. Update the messaging for [new context], refresh the assets, and rebuild the task list. Reference the original brief here: [link or attached file].
1.04 — Draft the messaging framework for a product launch
1.04 — Draft the messaging framework for a product launch
Draft a messaging framework for the launch of [product name]. Include: a one-sentence positioning statement, three key messages for each of these audiences: [audience 1], [audience 2], [audience 3], and two proof points per message. Reference the attached product brief.
1.05 — What would it take to launch this campaign in 5 new markets?
1.05 — What would it take to launch this campaign in 5 new markets?
We want to launch [campaign name] in these 5 new markets: [market 1], [market 2], [market 3], [market 4], [market 5]. For each, outline what needs to be localized (copy, assets, compliance), what can be reused, and what net-new work is required.
1.06 — Build a competitive analysis and surface gaps in our positioning
1.06 — Build a competitive analysis and surface gaps in our positioning
Research how [competitor 1], [competitor 2], and [competitor 3] are positioning themselves on [topic / product category]. Compare their messaging to ours at [our page URL or attached doc]. Identify: where we're stronger, where we're weaker, and any positioning angles they're using that we're not addressing.
1.07 — Track competitor messaging changes and alert me when they reposition
1.07 — Track competitor messaging changes and alert me when they reposition
Monitor the following competitor pages on a [weekly / monthly] basis: [URL 1], [URL 2], [URL 3]. Alert me whenever copy, pricing, or key messaging changes significantly. Summarize what changed and flag anything that affects our positioning.
1.08 — Which competitors get cited in AI answers where we're invisible?
1.08 — Which competitors get cited in AI answers where we're invisible?
Run a set of AI search queries for [topic / product category] on [ChatGPT / Perplexity / Google AI Overviews]. For each query, note which competitors are cited and whether we appear. Identify the 5 queries where we're most absent and competitors are most present, and recommend what content changes would improve our visibility.
1.09 — Summarize what our best-performing content has in common
1.09 — Summarize what our best-performing content has in common
Analyze our top [N] performing pages by [metric: organic traffic / conversions / engagement] over the last [time period]. Identify what they have in common: topic type, content length, heading structure, use of visuals, and CTAs. Summarize the patterns and recommend how to apply them to new content.
2.01 — Execute this campaign brief end-to-end
2.01 — Execute this campaign brief end-to-end
Run this campaign end-to-end per the attached brief and workflow diagram, following the Campaign Execution Guidance.
2.02 — Re-plan this campaign now that the launch date moved
2.02 — Re-plan this campaign now that the launch date moved
Our campaign launch date has moved from [original date] to [new date]. Review the current plan and re-sequence all tasks, asset deadlines, and go-live dates accordingly. Flag anything that can no longer be completed in time.
2.03 — Turn a creative concept into a multi-channel campaign brief and task list
2.03 — Turn a creative concept into a multi-channel campaign brief and task list
Turn this creative concept into a full campaign brief: [describe concept]. Include: campaign goal, target audience, channel plan (web, email, social, paid), asset list, key messages, and a task breakdown I can use to kick off work in Gradial.
2.04 — Spin up 100 custom landing pages for top CRM prospects
2.04 — Spin up 100 custom landing pages for top CRM prospects
Using this page as a template: [reference page URL], create personalized landing pages for each row in the attached CSV. Substitute [first name], [company], and [use case] into the hero and body copy for each.
2.05 — Clone our site structure for a new market
2.05 — Clone our site structure for a new market
Clone the page structure under [source folder path] into the [target locale/region path, e.g., /content/site/en-gb/]. Carry over the templates and components, then flag which pages need content localization before they can go live.
2.06 — What's the status of every active campaign and what's blocked?
2.06 — What's the status of every active campaign and what's blocked?
In [Jira / Workfront / Wrike], give me a status summary of all active campaign tasks. Show: what's in progress, what's overdue, what's blocked and why, and what's ready for review. Group by campaign.
2.07 — Intake this stakeholder request and turn it into tracked tasks
2.07 — Intake this stakeholder request and turn it into tracked tasks
Intake this request: [paste or attach the request]. Scope it into discrete tasks, estimate complexity for each, and create tickets in [Jira / Workfront / Wrike] under [project / board name]. Assign to [team / person] and set the target date to [date].
2.08 — Automate every Jira ticket I get asking for website updates
2.08 — Automate every Jira ticket I get asking for website updates
Set up automation so that any Jira ticket in [project key] with label [label name] or request type [type] automatically creates a corresponding Gradial task. Map the ticket fields [summary, description, URL, assignee] to the Gradial task fields.
2.09 — Show me all tickets waiting on web content changes this sprint
2.09 — Show me all tickets waiting on web content changes this sprint
In [Jira / Workfront / Wrike], show me all tickets in the current sprint that are waiting on a web content change. Include: ticket ID, title, who owns it, how long it's been waiting, and any linked pages or assets.
2.10 — Notify me in Slack when a page is ready for my review
2.10 — Notify me in Slack when a page is ready for my review
When this task is complete and the page is ready for review, send me a Slack notification in [channel name] with a link to the staged page and a summary of what changed.
2.11 — Set up an approval flow so legal signs off before anything publishes
2.11 — Set up an approval flow so legal signs off before anything publishes
Set up an approval workflow so that any task affecting pages in [folder path / tagged as compliance] requires sign-off from [legal reviewer role / person] before publishing. Route the review notification to [email / Slack channel].
3.01 — Turn a product one-pager into a full web page with FAQ and CTA
3.01 — Turn a product one-pager into a full web page with FAQ and CTA
Using this attached one-pager as the source, create a full web page at [target path] using [reference page URL] as the structural template. Add an FAQ section based on the most likely customer questions from the content, and include a CTA to [desired action / URL].
3.02 — Build a new landing page for a product launch
3.02 — Build a new landing page for a product launch
Build a new landing page for [product / campaign name] at [target path]. Use this page as a structural reference: [reference URL]. Write the headline, subhead, body copy, and CTA based on these key messages: [message 1], [message 2], [message 3]. Source on-brand hero and supporting images from the DAM at [folder path] or suggest alternatives.
3.03 — Refresh older blog posts with current stats and re-publish
3.03 — Refresh older blog posts with current stats and re-publish
Review all blog posts under [folder path] published in [year]. For each one: update outdated statistics with current figures, refresh any references to products or features that have since changed, and improve the meta description. Re-publish each post with today's date once updated.
3.04 — Build an FAQ section on this page from our support docs
3.04 — Build an FAQ section on this page from our support docs
Add an FAQ section to this page: [page URL]. Source the questions and answers from our support docs at [URL or folder path]. Select the 5–8 questions most relevant to the page topic and add them using the [FAQ component name] component.
3.05 — Create a PDP for a new SKU from a spec sheet
3.05 — Create a PDP for a new SKU from a spec sheet
Create a new product detail page for [product name / SKU] at [target path]. Use this PDP as a structural reference: [reference URL]. Populate it with content from the attached spec sheet. Use the DAM at [folder path] for product images.
3.06 — Create localized versions of this content for priority markets
3.06 — Create localized versions of this content for priority markets
Create localized versions of this page: [source page URL] for the following markets: [market 1 / language], [market 2 / language], [market 3 / language]. Translate the copy, adapt any region-specific pricing or offers, and ensure compliance text is included for each market. Place each at [target path structure].
3.07 — Rewrite thin-content pages to answer the query behind them
3.07 — Rewrite thin-content pages to answer the query behind them
Review these pages: [list of URLs]. For each one, identify the primary search query it's targeting, assess whether the current content adequately answers it, and rewrite any page that falls short. Prioritize factual depth, clear structure, and direct answers.
3.08 — Generate on-brand hero images for a campaign page
3.08 — Generate on-brand hero images for a campaign page
Generate a hero image for this campaign page: [page URL or campaign name]. Style: [describe visual style, e.g., clean product shot on white, lifestyle photography, abstract gradient]. Brand colors: [primary / secondary]. Dimensions: [e.g., 1440×600]. Save the output to [DAM folder path].
3.09 — Smart-crop the hero image for web, mobile, and social
3.09 — Smart-crop the hero image for web, mobile, and social
Smart-crop this image: [DAM path] for the following breakpoints and placements:
- Desktop hero: 1440×600 (keep subject centered)
- Mobile hero: 390×520 (keep subject in upper third)
- Social share: 1200×630 (square-safe zone)
- Instagram square: 1080×1080
Save all outputs to [DAM folder path].
3.10 — Generate product lifestyle images from a brief
3.10 — Generate product lifestyle images from a brief
Generate [number] lifestyle images for [product name] based on this brief: [describe scene, setting, target audience, mood]. Reference our brand style guide at [URL or attached file]. Output at [dimensions] and save to [DAM folder path]. Flag any outputs that don't meet brand standards for review.
3.11 — Create image variants from a source asset for different audiences
3.11 — Create image variants from a source asset for different audiences
Take this source image: [DAM path] and create variants for the following audience segments: [segment 1 — describe], [segment 2 — describe], [segment 3 — describe]. Adjust [copy overlay / color treatment / background] per segment while keeping the core composition. Save each variant to [DAM folder path] with segment name in the filename.
4.01 — Add tags to tagging taxonomy
4.01 — Add tags to tagging taxonomy
Add the following tags to the tagging taxonomy: [tag1] under [category, e.g., Content Type], [tag2] under [category, e.g., Page Classification], and [tag3] under [category, e.g., Campaign Theme]. Apply them to [content type, e.g., Campaign Theme, blog posts].
4.02 — Update tags in tagging taxonomy
4.02 — Update tags in tagging taxonomy
In the tagging taxonomy, rename the tag [old tag name] under [category] to [new tag name]. Also, move the tag [tag name] from [old parent category] to [new parent category] to reflect the updated classification structure.
4.03 — Update asset metadata
4.03 — Update asset metadata
For this asset: [asset path or name], update the description to [new description] and add the following tags: [tag1, tag2, tag3].
4.04 — Tag and organize 1,000 untagged assets in the DAM
4.04 — Tag and organize 1,000 untagged assets in the DAM
Review all untagged assets in [DAM folder path] and apply appropriate tags from our taxonomy. Use the asset content and filename to infer type, campaign, region, and subject matter. Flag any assets you're uncertain about for manual review.
4.05 — Find pages and campaigns still using the old logo
4.05 — Find pages and campaigns still using the old logo
Find every page and active email campaign using the old logo at [old DAM path] and replace it with the updated version at [new DAM path]. Report a list of everything changed.
4.06 — Find all pages using expired-license images and flag them
4.06 — Find all pages using expired-license images and flag them
Cross-reference the assets used on our live pages against this list of expired-license images: [attached CSV or list of DAM paths]. Flag every page that contains one and queue them for image replacement.
4.07 — Generate on-brand social cards for our next 10 blog posts
4.07 — Generate on-brand social cards for our next 10 blog posts
Create social share cards for these 10 blog posts: [list of URLs]. Use the [social card template name] template, pull the headline and hero image from each post, and save the outputs to [DAM folder path].
5.01 — Add and delete modules within emails
5.01 — Add and delete modules within emails
In this Marketo email: [email name or ID], add a [module name, e.g., Text + Image] module below the [existing module name or position]. Then delete the [module name or description] module that is no longer needed.
5.02 — Clone existing campaign with all settings
5.02 — Clone existing campaign with all settings
In Marketo, clone this campaign: [campaign name or ID] with all of its current settings, including smart list filters, flow steps, and schedule. Name the cloned campaign [new campaign name] and place it in [folder or program path].
5.03 — Schedule batch campaign
5.03 — Schedule batch campaign
In Marketo, schedule a batch campaign: [campaign name or ID] to run on [date and time, e.g., 2025-04-15 at 9:00 AM EST]. Use the existing smart list and flow settings. Set the person qualification rules to [run each person once / allow re-entry].
5.04 — Create emails from templates
5.04 — Create emails from templates
In Marketo, create a new email using the [template name] template. Populate it with the following content:
Subject line: [subject line]
Header: [header text]
Body: [body copy]
CTA: [CTA text and link]
Image: [image path or description]
5.05 — Build a 5-email welcome journey for new trial signups
5.05 — Build a 5-email welcome journey for new trial signups
Build a 5-email welcome journey in [Marketo / SFMC] for new trial signups. Use our brand voice guidelines and the following content themes:
Email 1 (Day 0): Welcome + getting started
Email 2 (Day 2): Key feature highlight
Email 3 (Day 5): Use case spotlight
Email 4 (Day 10): Community / resources
Email 5 (Day 14): Upgrade nudge
Reference this existing email for tone and structure: [example email name or URL].
5.06 — Localize an email campaign for priority markets
5.06 — Localize an email campaign for priority markets
Localize this email campaign: [campaign name or ID] for the following markets: [market 1], [market 2], [market 3]. Translate copy, adapt CTAs for regional offers, and ensure each version includes the required footer compliance text for that region.
5.07 — Re-engage subscribers who haven't opened in 90 days
5.07 — Re-engage subscribers who haven't opened in 90 days
In [Marketo / SFMC], build a re-engagement campaign targeting contacts who haven't opened any email in the last 90 days. Use a subject line that acknowledges the gap, offer [incentive or value prop], and suppress anyone who opens or clicks from future re-engagement sends.
5.08 — Write and schedule this month's newsletter
5.08 — Write and schedule this month's newsletter
Write and schedule this month's newsletter in [Marketo / SFMC]. Pull the top 3 blog posts from [URL or feed], include a spotlight on [product / campaign / event], and send to [list name] on [date] at [time, timezone]. Use the [newsletter template name] template.
6.01 — Single copy update
6.01 — Single copy update
On this page: [page URL], update the hero headline to [new headline text].
6.02 — Multi copy update
6.02 — Multi copy update
On this page: [page URL], update the hero headline to [new headline] and change the body text in the second section to [new body copy].
6.03 — Swap image(s) (upload asset)
6.03 — Swap image(s) (upload asset)
On this page: [page URL], replace the hero image with the attached file [filename.jpg] and swap the banner image in the promo section with [filename2.png].
6.04 — Swap image(s) (use DAM path)
6.04 — Swap image(s) (use DAM path)
On this page: [page URL], replace the hero image with the asset located at DAM path [e.g., /content/dam/images/hero-new.jpg].
6.05 — Update page with annotated screenshot
6.05 — Update page with annotated screenshot
On this page: [page URL], make the edits shown in the attached annotated screenshot.
6.06 — Update element style(s)
6.06 — Update element style(s)
On this page: [page URL], change the hero banner style from [current style] to [new style] and update the CTA button style to [new button style].
6.07 — Update page metadata
6.07 — Update page metadata
On this page: [page URL], update the page title to [new title], the meta description to [new description], and the SEO keywords to [new keywords].
6.08 — Create page variant
6.08 — Create page variant
Using this page as a reference: [source page URL], create a new variant with the following content changes: [list of localized/updated content].
6.09 — Multiple changes in one ticket
6.09 — Multiple changes in one ticket
On this page: [page URL], make the following changes:
(1) Update the hero headline to [new headline].
(2) Swap the hero image with [DAM path or attached file].
(3) Remove the [component name] section.
(4) Update the CTA link to [new URL].
6.10 — Insert component(s)
6.10 — Insert component(s)
On this page: [page URL], add a [component name, e.g., Text + Image] component below the [existing component name or position] with the following content: [content details].
6.11 — Remove component(s)
6.11 — Remove component(s)
On this page: [page URL], remove the [component name or description, e.g., the promotional banner below the hero section].
6.12 — Create new page (Word doc)
6.12 — Create new page (Word doc)
Create a new [page type, e.g., Article] page using this page as a reference: [reference page URL]. Populate it with the content from the attached Word document [filename.docx].
6.13 — Create new page (Figma)
6.13 — Create new page (Figma)
Create a new [page type, e.g., Landing Page] page using this page as a reference: [reference page URL]. Use the content and layout from this Figma link: [Figma URL].
6.14 — Create new page (URL)
6.14 — Create new page (URL)
Create a new [page type, e.g., Product Page] page using this page as a reference: [reference page URL]. Pull the content from this public URL: [source URL].
6.15 — Create new page (Prompt)
6.15 — Create new page (Prompt)
Create a new [page type, e.g., Campaign Page] page using this page as a reference: [reference page URL]. Use the following content:
Headline: [headline]
Body: [body text]
CTA: [CTA text and link]
Image: [image description or DAM path]
6.16 — Single copy update (content fragment)
6.16 — Single copy update (content fragment)
On this content fragment: [content fragment path], update the [field name] to [new value].
6.17 — Single copy update (experience fragment)
6.17 — Single copy update (experience fragment)
On this experience fragment: [experience fragment path], update the [element name] to [new text].
6.18 — Create content fragment
6.18 — Create content fragment
Create a new content fragment at [path] with the following fields:
[field1]: [value1]
[field2]: [value2]
[field3]: [value3]
6.19 — Create experience fragment
6.19 — Create experience fragment
Create a new experience fragment at [path] using this reference: [reference XF path]. Update the content to: [new content details].
7.01 — Run a QA report on this page before it goes live
7.01 — Run a QA report on this page before it goes live
Run a QA check on this page before it goes live: [page URL or staging URL]. Check for: broken links, missing images, metadata completeness, component rendering errors, and mobile display issues. Return a pass/fail summary with details on anything that needs fixing.
7.02 — Run an accessibility audit and queue the fixes
7.02 — Run an accessibility audit and queue the fixes
Run an accessibility audit on [page URL / site section]. Check against WCAG 2.1 AA standards. Return a list of violations organized by severity, and create tasks in Gradial for each fix.
7.03 — Find everywhere the brand guideline was violated and fix it
7.03 — Find everywhere the brand guideline was violated and fix it
Find every page where we're using [old brand element, e.g., the old logo / deprecated color / outdated typeface] and replace it with the updated version per our brand guidelines at [guidelines URL or attached doc].
7.04 — Monthly brand-consistency audit
7.04 — Monthly brand-consistency audit
Audit the following pages against our brand guidelines: [page URL 1], [page URL 2], [page URL 3]. Flag any copy, imagery, or styling that is off-brand and summarize the issues found.
7.05 — Standardize formatting on all legal and policy pages
7.05 — Standardize formatting on all legal and policy pages
Standardize the formatting on all pages in [folder path, e.g., /legal/]. Apply consistent H1/H2/H3 hierarchy, paragraph spacing, and link styling per our style guide. Flag any pages with content that needs human review before changes are applied.
7.06 — Add a compliance disclaimer to every product page in a region
7.06 — Add a compliance disclaimer to every product page in a region
Add the following EU compliance disclaimer to the footer of every product page under [regional folder path]: "[disclaimer text]". Apply only to pages that don't already include it.
8.01 — Find and replace (single page)
8.01 — Find and replace (single page)
On this page: [page URL], find all instances of [old term] and replace them with [new term].
8.02 — Find and replace (multi-page)
8.02 — Find and replace (multi-page)
Across the following pages: [page URL 1], [page URL 2], [page URL 3] — find all instances of [old term] and replace them with [new term].
8.03 — Bulk update (copy)
8.03 — Bulk update (copy)
Across the following pages: [page URL 1], [page URL 2], [page URL 3] — update [content element, e.g., component name] from [old value] to [new value]. Apply this as a batch task.
8.04 — Bulk update (assets)
8.04 — Bulk update (assets)
Across the following pages: [page URL 1], [page URL 2], [page URL 3] — replace the [component name] image with the asset at [DAM path or attached file]. Apply this as a batch task.
8.05 — Swap the seasonal banner across all regional homepages
8.05 — Swap the seasonal banner across all regional homepages
Swap the hero banner on all regional homepages to the [holiday/seasonal] promo using the asset at [DAM path]. Apply to: [list of locale URLs or folder path].
8.06 — Recurring find-and-replace check
8.06 — Recurring find-and-replace check
Across the following pages: [page URL 1], [page URL 2], [page URL 3] — find any instances of [outdated term] and replace them with [approved term]. Report which pages were changed.
8.07 — Scheduled batch email send
8.07 — Scheduled batch email send
In Marketo, run the batch campaign [campaign name or ID] using the existing smart list and flow settings. Confirm the number of people who qualified and the send status.
9.01 — Show me content decay: which pages are losing traffic
9.01 — Show me content decay: which pages are losing traffic
Analyze traffic trends across our site over the last 6 months and identify pages where month-over-month organic traffic has declined by more than [X]%. For each, note the probable cause and recommend whether to update, consolidate, or retire the page.
9.02 — Summarize this quarter's web performance for the board
9.02 — Summarize this quarter's web performance for the board
Summarize web marketing performance for [Q / date range]. Include: total traffic and trend, top-performing pages, conversion rates, and the top 3 initiatives that drove results. Format it as a one-page board summary.
9.03 — Which marketing channel is driving the highest-quality pipeline?
9.03 — Which marketing channel is driving the highest-quality pipeline?
Analyze pipeline attribution for [time period]. Compare channels by: lead volume, opportunity conversion rate, average deal size, and time to close. Identify which channel is driving the highest-quality pipeline and recommend where to shift investment.
9.04 — Weekly GEO visibility report
9.04 — Weekly GEO visibility report
Run a GEO report on [yourwebsite.com] and summarize how our brand visibility has changed since the last report.
9.05 — Is my site set up correctly for SEO?
9.05 — Is my site set up correctly for SEO?
Run a technical SEO audit on [domain URL]. Check for: crawlability issues, missing or duplicate meta titles and descriptions, broken internal links, redirect chains, pages blocked from indexing, and missing schema markup. Return a prioritized list of issues to fix.
9.06 — Write meta titles and descriptions for every page missing them
9.06 — Write meta titles and descriptions for every page missing them
Find every page in [folder path or site section] that is missing a meta title or meta description. Write SEO-optimized versions for each, using our brand voice and targeting the primary keyword for each page. Apply the updates.
9.07 — Fix all broken internal links and redirect chains
9.07 — Fix all broken internal links and redirect chains
Crawl [domain URL] and identify all broken internal links (404s) and redirect chains (3+ hops). Fix broken links by pointing them to the correct current destination. Simplify redirect chains to a single hop where possible.
9.08 — Make us visible in AI search for our key topics
9.08 — Make us visible in AI search for our key topics
Optimize our content for generative engine visibility on these topics: [topic 1], [topic 2], [topic 3]. For each, identify the pages most relevant to that topic, rewrite them to include clear factual statements and direct answers, and add structured data where applicable.
9.09 — GEO optimization (single page)
9.09 — GEO optimization (single page)
On this page: [page URL], optimize the content for generative engine visibility. Rewrite or supplement the content to include clear, factual statements, direct answers to likely search questions, and well-structured information about [topic or subject matter]. Prioritize clarity and specificity so the content is more likely to be cited by AI search tools.
9.10 — GEO Monitoring (ongoing visibility over time)
9.10 — GEO Monitoring (ongoing visibility over time)
Download the example prompt set (XLSX)
9.11 — Find every dead end and broken CTA in our signup flow
9.11 — Find every dead end and broken CTA in our signup flow
Audit our signup flow starting at [entry URL]. Walk every step and identify: broken CTAs, dead ends, form errors, pages that don't load correctly, and any steps where the journey stops unexpectedly. Return a list of issues with page URLs and descriptions.
9.12 — Create an A/B test for my landing page
9.12 — Create an A/B test for my landing page
Set up an A/B test on this page: [page URL]. Create a variant that changes [element, e.g., the hero headline / CTA copy / hero image] to [new version]. Define the success metric as [conversion event] and run the test until we reach statistical significance.
9.13 — Map the journey from ad click to purchase and identify drop-off
9.13 — Map the journey from ad click to purchase and identify drop-off
Map the full journey from [ad entry URL] through to [purchase confirmation URL]. Identify the steps where we see the highest drop-off, and for each one describe what the user experience looks like and what's likely causing the abandonment.
9.14 — Find where our mobile experience diverges worst from desktop
9.14 — Find where our mobile experience diverges worst from desktop
Compare the desktop and mobile experience across these key pages: [list of URLs]. Identify the most significant differences in layout, component rendering, and usability. Prioritize issues by impact and provide a fix recommendation for each.
9.15 — Show me which experiments won and roll the winners out site-wide
9.15 — Show me which experiments won and roll the winners out site-wide
Review all completed experiments run in the last [time period]. For each one that reached statistical significance, identify the winning variant and apply it to the full page population. Summarize the lift achieved for each.