Jamaica AggregatesJamaica AggregatesStrategy
INTELLIGENCE COMMAND CENTRE / BASELINE 01

Strategy

A living direction, grounded in evidence and open to revision.

6 Sept 2026 – 5 Oct 2026vs 7 Aug – 5 Sep · Pacific Time
Reporting dates

All time includes available history with each metric’s original dates. Other custom ranges need a matching report or analytics export.

Shared report baseline. Draft edits stay in this browser and are not shared with other visitors. Export a snapshot to retain them.
Confirmed business goal

Generate measurable demand for sand and gravel.

Build a digital ecosystem that generates measurable demand and enquiries for Jamaica Aggregates, eventually connecting enquiries to quotes, orders and revenue.

The demand-generation system

The intended journey; the connections below are not yet live.

Confirmed dataPartial dataNot measured

Select a stage to explore the evidence and the next tracking step. This pathway shows data availability, not conversion rates.

Clicks, landing-page views and calls placed are supporting signals. Enquiries, quotes, orders and revenue need their own verified records.

Working strategy

All directions are proposed. Approval, ownership and numerical business targets are still open.

ProposedMeasurement strategy

Measure demand before optimising reach

Prioritise an agreed enquiry definition and a simple enquiry-to-quote record. Use views, clicks, follows and platform calls as supporting indicators until commercial outcomes are verified.

ProposedFacebook strategy

Facebook: paid reach with local organic tests

Keep paid delivery visible as its own contribution. Test community, people and real operations content organically, while avoiding conclusions from one responsive post.

ProposedInstagram strategy

Instagram: practical education and participation

Test useful sand and gravel education, questions and short real-world videos. Review saves, questions, organic views and recorded enquiries separately from boosted results.

ProposedContent strategy

Broaden the mix before choosing winners

Build small tests across education, projects, operations, people, behind the scenes, community and FAQs. Treat safety content as requiring current expert review. No production schedule is approved.

ProposedAudience strategy

Validate buyers through enquiry data

Use contractor, developer, procurement and homeowner groups as interview and enquiry-log hypotheses. Do not treat social follower demographics as customer demographics.

ProposedPaid-media strategy

Location-led demand with verified fulfilment

Plan campaigns around confirmed locations and service areas, then compare qualified enquiries by product and parish. Current parish ad views establish delivery, not sales potential.

ProposedInstitutional memory

Make every campaign leave a useful record

Store what ran, why, what it cost, what happened, what was learned and what comes next. Keep approvals, rejected ideas and missing outcomes visible.

Measurement roadmap

Target architecture for the next phases. No integration is connected.

01

Agree the enquiry record

Define enquiries, qualified leads and follow-up responsibilities; record product, parish, contact route and source where known.

Future / not connected

Manual enquiry log

A reviewed sample of genuine enquiries with consistent definitions.
02

Audit the website measurement base

Inventory existing tracking before proposing changes. Plan GA4 and Google Tag Manager with approved events, access and privacy controls.

Future / not connected

Google Analytics 4 · Google Tag Manager

Verified event definitions and a documented test visit; no duplicate event firing.
03

Measure contact attempts

Plan website form, click-to-call and WhatsApp-link events. Keep contact attempts separate from conversations, enquiries and qualification.

Future / not connected

Website forms · Click-to-call · WhatsApp-link events

Tested contact events reconciled to their destination, with clear event limitations.
04

Connect campaign and website signals

Plan consistent campaign tagging, Meta Pixel and Google Ads conversion tracking where accounts and lawful event use are confirmed.

Future / not connected

Campaign tagging · Meta Pixel · Google Ads conversion tracking

Tested campaign visits and verified platform event receipts with deduplication where required.
05

Evaluate server-side events when appropriate

Assess Meta Conversions API only after event definitions, consent, ownership, deduplication and technical feasibility are established.

Future / not connected

Meta Conversions API, if appropriate

A reviewed decision on feasibility followed by independently verified event delivery if implemented.
06

Follow enquiries through the commercial journey

Link qualified enquiries to quotes and orders using permissioned business records; add revenue only when reliable values and attribution limits are documented.

Future / not connected

Enquiry log · Quote records · Order records · Revenue records

A validated enquiry-to-quote-to-order sample and an explanation of unmatched or unknown sources.