An itemised implementation plan for the website, measurement, advertising accounts, enquiry handling, Ruddr and Power BI. Each step has an owner and a reviewable completion check.
This is the proposed delivery checklist for Integra’s production website and systems. It records what RainRocks will configure and what Integra will supply or approve; it is not a claim that these accounts or integrations are already connected.
The checklist explains the existing implementation scope. Setup remains CAD $13,505.90; the monthly service remains CAD $4,362.47. Media remains separate at CAD $2,000 per month: LinkedIn $1,200, Google Search $800 and Meta $0. Hosting, software, approved connectors and tax are additional. New server-side ad integrations or expanded source/account coverage require agreement.
Workstreams overlap within the indicative eight-week build. Missing access, platform verification, paid-connector approval or content sign-off can move dependent tasks. Campaigns start after readiness and approval; the first 90 campaign days run from that point.
| System | Client-owned access / decision | RainRocks uses it to |
|---|---|---|
| Domain, CMS and hosting | IT owner; DNS changes or delegated access; current-site export and backup permissions. | Build staging, preserve URLs, verify ownership and launch reversibly. |
| Google measurement and search | GA4, GTM and Search Console invitations; correct account/property IDs. | Reuse history, configure events, verify the domain and report website/search performance. |
| Google Ads | Account access, billing/advertiser verification and campaign approval. | Prepare and operate the CAD $800 monthly Search allocation. |
| Meta | Business Portfolio/Page permissions; relevant dataset/ad-account review. | Enable organic operations and agreed measurement readiness; paid spend stays $0. |
| Page/Campaign Manager roles, lead access, billing and approved audience/offer. | Prepare the CAD $1,200 campaign and a tested website/native-form lead route. | |
| Ruddr and sales | Workspace admin/API permissions, stage/field decisions, sales owners and approved import. | Validate supported writes, map leads, prevent duplicates and track progression. |
| Microsoft / Power BI | Workspace and source permissions; viewer licences; sharing requirements. | Build one model and six authenticated report pages. |
| Email and content | Sending-domain owner, email-platform access, consent/suppression records and content approvers. | Authenticate sending, connect signups and prepare approved publishing workflows. |
RainRocks prepares configuration and test evidence. Integra retains ownership, accepts platform terms, provides billing, approves claims/privacy wording and names the sales follow-up owner. Account access is granted by invitation rather than sending passwords.
Open a workstream to review its steps. Each “Complete when” line is the evidence used during acceptance, not a live status indicator.
Timing: Weeks 1–2
Owner: RainRocks project lead + Integra account owner
Access needed: Existing account IDs, business details, named sales/IT/finance contacts and delegated invitations.
Depends on: Project commencement and nominated decision makers.
Step 01
Record the domain, CMS, hosting, analytics, advertising, social, email, Ruddr and Microsoft accounts already in use. Reuse suitable assets and preserve their history.
Complete when: An account register with IDs, owners, access status and recovery contacts.
Step 02
Confirm the legal entity, billing contact, CAD reporting and Calgary business timezone. Review platform-specific currency and timezone restrictions before creating any new ad account.
Complete when: Integra-approved account and billing settings; no duplicate ad accounts.
Step 03
Integra retains ownership. Invite named RainRocks users or partner accounts with the permissions needed for setup; use MFA and retain an Integra backup administrator.
Complete when: Invitations accepted and required tasks verified; no shared personal passwords.
Step 04
Confirm 15 core pages, four reusable templates, four form types, up to 20 migrated content entries, one Ruddr workspace/pipeline and six Power BI pages. Assign content and campaign approvers.
Complete when: Signed scope, access list, approval dates and change-control route.
Step 05
Check Ruddr features/API access, Microsoft licences, hosting, email platform and any paid connectors against the proposed design before purchase.
Complete when: A connection register showing route, cost, owner and any agreed fallback.
Timing: Weeks 1–4
Owner: RainRocks web lead + Integra IT/content owners
Access needed: Domain/DNS access, existing CMS inventory, brand assets, approved copy and customer-story permissions.
Depends on: Account inventory and approved page plan.
Step 06
Export or back up available content and settings, inventory current URLs and preserve existing stories. Add supplied analytics/Search Console priorities to the redirect decisions.
Complete when: Baseline inventory, restorable source/backup and approved URL map.
Step 07
Configure the agreed hosting/CMS, HTTPS and a protected preview. Document DNS records and a rollback path before changing the live domain.
Complete when: Working preview, certificate check and reversible cutover instructions.
Step 08
Create the 15 approved core destinations and four reusable templates. Add navigation, service links, proof, calls to action and useful 404/confirmation states.
Complete when: Page inventory mapped to the website chapter, with no unfinished placeholders.
Step 09
Move up to 20 approved articles/stories, retaining valuable URLs where practical. Review images, alt text, dates, author information and links.
Complete when: Migration reconciliation against the approved list and signed-off content.
Step 10
Set page-specific titles, descriptions, visible headings, canonical URLs, appropriate structured data, robots rules and XML sitemap. Implement approved one-hop redirects.
Complete when: Crawl and redirect checks; live client-site indexing intent explicitly approved.
Step 11
Review mobile layouts, keyboard access, labels, focus, images and representative performance. Check contact details, downloads, links and forms before content sign-off.
Complete when: A resolved launch issue list and recorded desktop/mobile checks.
Timing: Weeks 2–4
Owner: RainRocks analytics lead + Integra privacy/IT owner
Access needed: GTM publishing access, the agreed consent platform/policy and approved measurement purposes.
Depends on: Account register and draft forms; this precedes ad-tag activation.
Step 12
Agree events, source fields, conversion definitions, retention and who can view each dataset. Keep identifiable enquiry content out of analytics events and URLs.
Complete when: An event dictionary with trigger, purpose, parameters and destination.
Step 13
Define utm_source, utm_medium, utm_campaign and utm_content conventions. Preserve permitted click IDs and original/latest source fields through the form journey.
Complete when: A link builder and tested examples for Google, LinkedIn, email and organic social.
Step 14
Reuse or create the client-owned GTM web container. Inventory existing hardcoded/CMS tags, remove duplicate measurement routes and document container IDs.
Complete when: One documented deployment route, checked using Tag Assistant.
Step 15
Connect the approved consent controls and configure Google consent defaults/updates before dependent measurement. Apply explicit consent checks to non-Google tags and test withdrawal.
Complete when: A consent test matrix covering initial, accept, reject and changed choices.
Step 16
Test triggers in preview, keep staging/test activity distinct, then publish an identified container version only after approval.
Complete when: Tag map, test log, published version and a rollback version.
Platform references: S50
Timing: Weeks 3–5
Owner: RainRocks analytics lead + Integra Google account owner
Access needed: GA4 property access sufficient to configure the agreed website stream and links.
Depends on: Measurement dictionary, consent decisions and GTM installation.
Step 17
Reuse the correct GA4 property where suitable; otherwise create the agreed client-owned property and web stream. Confirm production domain, timezone and currency.
Complete when: Property ID, stream ID and measurement ID recorded against the correct site.
Step 18
Deploy through the approved single tag route. Review enhanced measurement, referral behaviour and any external booking domains against the actual journey.
Complete when: A diagnostic session with expected page views and no duplicate installation.
Step 19
Emit generate_lead for an accepted, successfully saved consultation/project enquiry. Keep resource/signup actions distinct; automatic form events or button clicks alone do not establish a valid lead.
Complete when: A labelled accepted test appears once; validation failures and spam do not produce this event.
Step 20
Set agreed key events, internal/test traffic handling and product links. Check Realtime/DebugView and processed reports when available; document consent-related measurement gaps.
Complete when: Baseline acquisition/event views and test evidence; reporting delay is recorded.
Platform references: S48
Timing: Weeks 2–6
Owner: RainRocks SEO lead + Integra DNS/Google owner
Access needed: Existing Search Console access or approval to add the required DNS verification record.
Depends on: Domain ownership confirmed; production checks follow website launch.
Step 21
Reuse existing access or verify a Domain property through DNS. If only a URL-prefix property is practical, document its exact protocol/host coverage and limitation.
Complete when: Integra-owned verified property; existing owners and verification tokens preserved.
Step 22
Grant appropriate working access and link the relevant GA4 property where suitable. Record the property used by the reporting connection.
Complete when: Property, access and reporting source recorded in the account register.
Step 23
After launch, check robots/canonical/indexing intent and submit the live XML sitemap. Inspect priority service pages and changed URLs.
Complete when: Sitemap acceptance and URL-inspection notes; issues assigned for correction.
Step 24
Capture available query/page performance, indexing and enhancement issues. Review changes after data accrues rather than promising immediate indexing or rankings.
Complete when: Dated baseline and a post-launch review task.
Timing: Weeks 4–7
Owner: RainRocks paid-media lead + Integra account/billing owner
Access needed: Google Ads working access, billing/verification completion, approved offer and landing page.
Depends on: Saved-enquiry event, consent checks and an approved destination page.
Step 25
Reuse the appropriate account, connect agency access and confirm billing, advertiser verification, location, currency and timezone settings.
Complete when: Client-owned account with billing/verification status and working access recorded.
Step 26
Link the correct GA4 property and check auto-tagging. Choose one primary enquiry conversion route: GA4 import or native Ads measurement. Keep duplicate/diagnostic actions observational and review campaign goals.
Complete when: One tested primary acquisition definition; custom goals checked for unintended bidding signals.
Step 27
Create the agreed high-intent groups, location settings, negatives, relevant ads/assets and tagged landing links. Map enquiries back to the selected service.
Complete when: Paused campaigns and an approved targeting/keyword/creative checklist.
Step 28
Translate the allocation into platform budgets and a shared pacing control. Review spend against the combined CAD $2,000 monthly media cap.
Complete when: Budget sheet, alerts and named pause/escalation owner; platform daily budgets are not represented as a hard monthly cap.
Step 29
Check landing pages, conversion diagnostics and policy status; obtain Integra campaign approval before activation. Review search terms, delivery and recorded lead quality after launch.
Complete when: Launch approval, campaign IDs and first-week review booked.
Timing: Weeks 3–6
Owner: RainRocks social lead + Integra Meta business owner
Access needed: Business Portfolio, Facebook Page and relevant Instagram/dataset access; billing only if paid activation is later approved.
Depends on: Account ownership, consent decisions and channel plan.
Step 30
Inventory the existing Meta Business Portfolio, Facebook Page, any linked Instagram account, ad account and dataset. Resolve ownership and invite approved partner/users.
Complete when: An asset/access map; no replacement account created simply to bypass access issues.
Step 31
Review any existing dataset/pixel and domain verification requirement. Document the approved events, privacy purpose and whether installing a new pixel is justified while paid Meta is inactive.
Complete when: An explicit install/reuse/defer decision and dataset ID if enabled.
Step 32
If enabled, deploy consent-aware browser measurement and verify events in the platform tools. A server-side Conversions API route is assessed separately; it is not assumed to be a native Ruddr feature.
Complete when: Event/consent evidence or a documented deferral. Any added server route requires approved scope and deduplication design.
Step 33
Connect the Page for organic publishing/reporting where supported. Prepare any later paid activation requirements, but allocate CAD $0 to Meta under this plan.
Complete when: Organic access checked and no paid Meta campaign activated; any future spend is separately approved.
Platform references: S53
Timing: Weeks 4–7
Owner: RainRocks paid-media lead + Integra Page/ad account owner
Access needed: LinkedIn Page and Campaign Manager permissions, billing, lead access and approved audience/offer.
Depends on: Agreed measurement, landing page or native lead-form route.
Step 34
Reuse the client account and associate the correct Page. Confirm working roles, lead access, billing, currency and timezone before configuring campaigns.
Complete when: Account/Page IDs and permissions verified by the people responsible for each task.
Step 35
Install or reuse the Insight Tag under the consent plan. Define the saved-enquiry conversion and check it against the chosen campaign destination.
Complete when: Tag diagnostics and a labelled website-conversion test, with attribution settings recorded.
Step 36
Approve the offer and fields. For native Lead Gen Forms, connect an approved supported lead-delivery tool or establish a controlled export/import process with an owner and response check.
Complete when: A test native lead reaches the agreed intake route. New Lead Sync API approval is not assumed.
Step 37
Start with one focused audience/offer, relevant creative, geography and exclusions. Record campaign pacing alongside the Google allocation.
Complete when: Paused campaign, budget/targeting sheet and approved creative/form or landing page.
Step 38
Confirm the lead recipient can access submissions and follow up. Obtain campaign approval, then review delivery, lead fit and sales feedback before expanding targeting.
Complete when: Approval, active campaign IDs and a first-week lead-quality review.
Timing: Weeks 3–6
Owner: RainRocks integration lead + Integra Ruddr admin/sales owner
Access needed: Ruddr plan/API permissions, field/stage decisions, approved contact import and follow-up owners.
Depends on: Form definitions, source/consent fields and a verified integration route.
Step 39
Implement consultation, project brief, resource/webinar and newsletter forms with relevant fields, validation, spam controls and accessible success/error states.
Complete when: Each form tested for valid, invalid and rejected-spam submissions.
Step 40
Persist an accepted enquiry with a submission ID, time, form/service, permitted source data and consent record. Give users a truthful confirmation only after the save succeeds.
Complete when: A retrievable test record; no analytics lead event on a failed save.
Step 41
Agree one pipeline of up to eight stages, required fields, qualification criteria, next-action dates and owners. Validate the available Ruddr workspace features before promising automation.
Complete when: Stage/field map and a worked example from new enquiry to won/lost outcome.
Step 42
Map company/contact fields, test deduplication and import up to 1,000 supplied contacts/companies after a sample review. Preserve original data and import provenance.
Complete when: Import totals, exceptions and duplicates reconciled against the supplied file.
Step 43
Use verified Ruddr API/connector operations for the supported entities. Where an opportunity write is unsupported, use a tracked manual handoff or agree another route before implementation.
Complete when: One saved test is linked to the correct company/contact and sales owner without an invented API capability.
Step 44
Keep a failed delivery in a visible retry/exception queue and use an idempotent submission key to prevent duplicates. Record qualification, opportunity value, won/lost and project linkage where supported.
Complete when: Failure/retry test, one resulting record and a sales owner able to update the outcome.
Timing: Weeks 3–7
Owner: RainRocks content lead + Integra sender/Page owners
Access needed: Email-platform access, sender-domain DNS, approved consent/suppression records and social Page permissions.
Depends on: Approved brand, forms and content approval workflow.
Step 45
Configure or validate the email provider’s SPF/DKIM requirements and review DMARC alignment with Integra IT. Preserve existing mail-provider records.
Complete when: Provider authentication checks and a controlled test message.
Step 46
Map signup fields, service/resource requests, marketing choices and unsubscribe/suppression rules. Never treat a project enquiry as automatic newsletter permission.
Complete when: Signup, unsubscribe and suppression tests; contacts retain their recorded choices.
Step 47
Prepare reusable email/social layouts, tracked links, approval and scheduling roles. Confirm Page connections and available organic reporting permissions.
Complete when: An approved template set, content calendar and scheduling/access test.
Step 48
Plan two articles, two email campaigns, three LinkedIn posts and two Facebook posts per week. Obtain content approval before scheduling or sending to real audiences.
Complete when: Approved first-month production checklist and documented approval deadlines.
Timing: Weeks 4–7
Owner: RainRocks reporting lead + Integra Microsoft/data owner
Access needed: Microsoft workspace/licences, approved read access, connector decisions and metric owners.
Depends on: Source definitions and tested intake/Ruddr mapping; source access determines available data.
Step 49
For the agreed account/property per source, record how GA4, Google Ads, Search Console, LinkedIn, Meta/social, email, saved enquiries and Ruddr reach the reporting layer.
Complete when: Route, fields, cadence, permissions, cost and available history for every source; approved exports cover restricted APIs.
Step 50
Use supported OAuth/API/connector access with secrets kept server-side. Separate contact-level lead data from aggregate campaign measures and retain a controlled retry/error log.
Complete when: Access review, field inventory and test extracts; no credentials in public pages or report exports.
Step 51
Define the grain for spend, events, leads, opportunities and projects. Join with stable IDs, keep original/latest attribution distinct and prevent many-to-many joins from multiplying spend or revenue.
Complete when: Metric dictionary and sample reconciliations back to source totals.
Step 52
Deliver executive overview, paid acquisition, website/search, content/social/email, sales pipeline and project/commercial performance views, using available approved source fields.
Complete when: Six reviewed pages with filters, definitions, source dates and explicit unavailable-data states.
Step 53
Target an initial daily scheduled refresh where source and licence limits permit. Stagger extraction/model refresh and show the last successful source/update time.
Complete when: Successful refresh history plus a tested failure notification and named recovery owner.
Step 54
Use authenticated Microsoft workspace/app access, appropriate roles and row-level controls where needed. Confirm viewer licensing; do not use public Publish to Web for sales/client data.
Complete when: Integra users can see the intended views, restricted users cannot, and the operating guide is delivered.
Timing: Weeks 7–8 + post-launch checks
Owner: RainRocks delivery lead + Integra sales/IT/marketing approvers
Access needed: Content sign-off, campaign approval, DNS window, named sales owner and launch acceptance.
Depends on: Website, measurement, lead handoff and reporting acceptance evidence.
Step 55
Use clearly labelled synthetic requests from tagged campaign links and any selected native lead form. Trace the saved enquiry to the Ruddr handoff, assigned follow-up and Power BI model.
Complete when: A reconciled test log with source, submission and destination IDs; tests excluded from commercial results.
Step 56
Test rejected consent, invalid forms, duplicate delivery, save failure, expired integration access and refresh failure. Confirm essential enquiry handling works independently of optional analytics consent.
Complete when: Expected outcomes, visible exceptions and an accountable recovery action for each scenario.
Step 57
Check page/form acceptance, redirects, production indexing intent, analytics diagnostics, sales ownership and approved media pacing. Keep ad campaigns paused until their own acceptance/approval is complete.
Complete when: A dated go/no-go checklist accepted by Integra’s nominated approvers.
Step 58
Apply the agreed DNS/hosting cutover, verify HTTPS and priority routes, submit the live sitemap and recheck real production forms using labelled tests. Retain the prior site/rollback option through the agreed window.
Complete when: Live checks recorded; any rollback decision has a named owner.
Step 59
Hand over account ownership/access register, URL/redirect list, tag/event dictionary, connector map, form/pipeline rules, report definitions, training and incident contacts.
Complete when: Integra can edit content, process a lead, review a report and request help.
Step 60
Start the retainer on the agreed readiness date. Check the first week’s delivery and the first 30/60/90 campaign days, reviewing actual lead quality, spend and sales progression.
Complete when: First monthly checklist and review dates; the campaign clock begins at readiness/launch, not automatically at build commencement.
| Measure | Definition / trigger | How it is used |
|---|---|---|
| Page / CTA engagement | A viewed page or clicked call/email/resource link. | Useful engagement evidence; not a saved enquiry or revenue. |
| Saved website enquiry | Accepted consultation/project form saved successfully; one submission ID. | GA4 generate_lead and the agreed ad-conversion route where measurement is permitted. |
| Native LinkedIn lead | A submitted Lead Gen Form received through the approved intake route. | A separately identified native source; deduplicated into intake rather than requiring a website GA4 event. |
| Resource / newsletter action | A resource request or separately consented subscription. | Reported separately from a sales enquiry unless the agreed qualification rule is met. |
| Qualified lead / opportunity | Sales owner confirms fit and records the agreed stage/value. | Pipeline reporting using sales records; not inferred from an ad-platform conversion. |
| Won revenue / project result | Supported won/project/commercial fields updated by the responsible owner. | Commercial reporting with explicit revenue/cost definitions and source dates. |
Ad platforms can attribute the same enquiry differently. Power BI shows platform-attributed conversions separately from deduplicated saved leads and sales outcomes; platform totals are not added together as unique customers. Daily refresh and consent restrictions mean the views will not always match live platform screens.
The launch pack brings together the approved website, consent/tag checks, every active form’s saved record and owner route, tested sales handoff, report reconciliation and campaign/budget approval. A connection that cannot yet be completed is recorded with an owner and an agreed fallback before acceptance.
The monthly checklist then covers connection/refresh checks, campaign pacing and optimisation, search/indexing review, content production, lead-quality feedback and the agreed website/report improvement allowances. Setup builds the system; the managed service keeps the information usable and the activity accountable.