01 | Build your site + first landing page Use @Sites to build a reusable landing-page website for our outreach team. Start by asking only for missing information that affects the first page. OUR BRIEF Team / organization: [NAME] Audience and language: [AUDIENCE, REGION, LANGUAGE] Offer or topic: [WHAT THE VISITOR WILL RECEIVE] Ad promise: [THE MESSAGE THAT BRINGS THEM HERE] One main call to action: [ACTION + REAL DESTINATION URL] Brand reference: [ATTACHED BRAND GUIDE OR WEBSITE] Approved claims / resources: [LINKS OR ATTACHMENTS] BUILD THE FOUNDATION Create one site that can host multiple campaign landing pages at stable, readable URLs. Keep design, navigation rules, and shared tracking in one reusable foundation. Build the first page and a reusable template. Future pages must preserve the original pages and their URLs. Use the supplied brand. If none is supplied, propose a simple palette, typography, and tone for my review. Write plain, respectful, accurate copy. Match the page headline and offer to the ad promise. Use one clear primary action, readable mobile typography, accessible contrast, labeled controls, visible keyboard focus, and fast-loading images. Add only approved proof or testimonials; never invent outcomes or endorsements. Make the call to action work. Prefer my existing registration or contact destination. Do not add a form that silently discards submissions. If a form is necessary, ask where submissions should go and confirm the real success state. Explain if an external destination prevents observing completion. Leave a shared place for Analytics and advertising tags, but do not invent measurement IDs, add placeholder tracking, or send personal details in event data. Ask what privacy and consent approach our team uses before enabling measurement. Show me the first page, the reusable structure, and a brief verification report covering mobile layout, links, the action, and the success state. Ask me to approve the first public publication. After approval, publish and verify the real page URL. Summarize how I can request the next landing page. 02 | Connect Google Analytics Help me connect our existing landing-page site [SITE URL] to Google Analytics 4. Open analytics.google.com in the available browser. Let me take over for sign-in and any account terms. Help me select the correct account and create or select the property and web data stream for this site. Ask for the reporting time zone and currency if they are not established. Do not create duplicate properties or streams without checking. Inspect the site's current tracking first. Reuse an existing Google tag or Tag Manager setup when appropriate. Use the actual measurement ID from this property and place the required setup in the site's shared layout so future landing pages inherit it. Follow our agreed consent configuration; do not send names, email addresses, prayer requests, or other personal details in URLs or event parameters. Define a simple measurement plan: landing-page visit, primary-action click, and confirmed completion if that success state is observable. Ask which action is our key event. If registration finishes on a different website, explain the measurement gap and the access needed to measure it. Do not count an outbound click as a completed registration. Show the changes before publishing. After I approve, test the published site with Tag Assistant and Analytics Realtime or DebugView as appropriate. Report the property, stream, test action, observed event, and anything still waiting for data. Distinguish installation from verified collection. Save the measurement plan for future pages. 03 | Set up Google Ads conversion tracking Help me configure conversion measurement for [GOOGLE ADS ACCOUNT] and [SITE URL]. Our intended conversion is [ACTUAL SUCCESSFUL ACTION]. Open ads.google.com and let me sign in. Verify the account before changing anything. Inspect existing conversion actions and the site's current Google tag / GA4 setup. Do not duplicate an existing conversion or blindly install another base tag. Explain the best route for this site: import the relevant key event from a linked GA4 property, or configure a direct Google Ads conversion. Recommend one primary measurement path for this outcome and explain the choice. Confirm the conversion definition, counting method, value if relevant, and whether it is primary for bidding. Do not enable enhanced conversions or upload customer data without a separate decision. After I approve the setup, use the actual account IDs and labels from Google. Reuse the existing tag where appropriate and add the destination or event configuration needed. Fire the completion event only on a real successful action. If the action happens on another domain, explain what can and cannot be verified with our current access. Test the published page and completion path. Report the event or tag observed, the diagnostics result, and any reporting delay. Record whether this conversion comes from GA4 or Google Ads. Do not claim an attributed ad conversion just because a test event fired. Do not launch campaigns or change budgets as part of this setup. 04 | Connect ChatGPT to Ryze AI Help me connect this ChatGPT workspace to Ryze AI for our advertising workflow. Open the official Ryze site at get-ryze.ai and let me register or sign in. Help me connect only the ad accounts and GA4 property I select. I will complete sign-in, consent, and account authorization myself. Check which Ryze app or MCP connection is supported in my current ChatGPT account. Prefer the available Ryze app. If a custom MCP connection is required, use Ryze's current official setup instructions, verify its server address and OAuth flow, and explain any workspace-admin requirement. Do not guess that a connection succeeded or ask me to paste passwords or access tokens into chat. After connection, list the available ad accounts and analytics properties with their names, IDs, currencies, time zones, and available reporting access. Identify which supported tools can read data and which can change campaigns. If a service is missing, tell me exactly what is missing and the next step. Run a read-only report for the last seven completed days for the account I select. Show spend, clicks, conversions, and cost per conversion where available. Use the actual conversion definition and flag unavailable metrics. Make no campaign changes yet. Save a short connection summary so future tasks use the correct accounts. 05 | Train Dot to report every day Act as our advertising analyst. Use the Ryze-connected accounts [ACCOUNT NAMES / IDS] and Analytics property [PROPERTY]. Our goal is [GOAL], and our primary conversion means [DEFINITION]. Prepare a morning report at [TIME] in [TIME ZONE], delivered in [DESTINATION]. First run a sample for review. Once we agree on the format, create the recurring task if supported and show me the saved timing, scope, and delivery destination. If scheduling is unavailable, say so and leave me a reusable manual workflow. For each run, use completed reporting periods. Compare yesterday with the previous comparable day, and the last seven completed days with the preceding seven. State dates, currency, account time zone, source, and data freshness. Report spend, clicks, conversions, conversion rate, and cost per conversion when available. If conversions are zero, show cost per conversion as undefined, not zero. Keep platform-attributed results separate; do not add them together as unique people. Identify waste, unusual changes, tracking gaps, and landing-page drop-offs. Distinguish missing data from zero results. Flag small samples and conversion delay. Do not infer training completion or meaningful engagement from an account creation alone. Finish with at most three recommended actions. For each, give the evidence, proposed change, expected benefit as a hypothesis, and how we would evaluate it. Include one clear decision for me when needed. This reporting task is read-only: do not change campaigns, budgets, targeting, pages, or tracking. Do not send reports to other people unless I explicitly name them and authorize delivery. 06 | Review, act, and gradually delegate Help me gradually delegate advertising decisions to our agent team. Use these responsibilities: - Brand Manager Bot: maintain approved voice, design templates, and truthful claims. - Ad Bot: analyze performance and propose or execute explicitly permitted campaign changes. - Funnel Expert Bot: check message alignment, landing-page behavior, and measurement. These can be roles within one agent; do not assume separate bots have been created. Review our recent reports and correction history. Propose one small category of decisions that may be ready for delegation. Do not assume permission from this request to change live campaigns. Draft a decision agreement covering the exact account and campaign scope, permitted actions, forbidden actions, budget and change limits, minimum evidence, review frequency, stop conditions, and what requires my approval. Ask me to fill in any missing limits. Do not invent a spend allowance. Keep new campaigns, budget increases, deletion, broader targeting, and tracking changes outside autonomous scope unless I explicitly include them. After I approve the agreement, confirm that the connected tools support it. For each permitted change, record the before state, reason, action, timestamp, after-state verification, and next review date. Stop and ask if data is missing, tracking looks broken, or the action would exceed the agreement. Report the actual result; do not promise a performance improvement. Review outcomes with me and recommend whether to retain, narrow, or expand the scope.