Mobile app marketing · Marketing
Your app marketing should bring people back to book or buy.
A dealer downloads your ordering app but never places an order. A customer installs your booking app, looks around, and leaves. Paying for more installs will not explain where either person stopped.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

In one paragraph
Mobile app marketing brings people to your Android or iOS app through paid campaigns and encourages useful activity after installation. GullySales sets up install campaigns and permission-based return messages, connects them to in-app event tracking, and reports on completed actions and return usage rather than treating every download as a sale.
Your campaigns need a clear action to work towards, such as a first order or a completed booking. The app must report that action, and the message after installation must give someone a reason to return.
GullySales connects acquisition campaigns with onboarding and re-engagement messages. App store optimisation is separate work, although the advertisement and store listing need to make the same promise.
Who it is for
This is written for you if these sound familiar.
- B2B sellers with an existing dealer or customer app and an identifiable audience to reach
- Consumer app owners whose downloads are growing without a rise in useful activity
- Businesses launching a working app with registration and purchase tracking ready to test
- Subscription apps that need people to return after their first session
- Booking or ordering apps running install campaigns without a return-message plan
Before you decide
When this may not be the right fit.
- Businesses without a working app, because app development is outside this service
- Owners buying download counts without measuring what happens after installation
- Apps with broken registration or checkout that need product fixes before more traffic
The problem
Does this sound like your business?
Common situations this work addresses.
“Downloads without orders”
Your dashboard shows installs, but your order records show little movement. Without registration and purchase events, you cannot separate people exploring the app from people ready to buy.
“Campaigns chasing the wrong action”
A campaign judged only on installs has no evidence of who becomes a paying customer. The chosen event must reflect useful activity and be available for campaign optimisation.
“Silence after the first open”
Someone registers, then hears nothing relevant again. A return message needs a reason to act, permission to reach that person, and a destination inside the app.
“A different promise in the store”
The ad promotes easy repeat ordering, but the store listing talks about unrelated features. That mismatch leaves people unsure what they are downloading.
Choose the right scope
Start with the work your business needs.
New app acquisition
For a working app entering the market, the starting scope establishes events and tests acquisition against a meaningful first action. A dealer ordering app might use first order rather than registration, provided that event is available and suitable.
Install campaign correction
For an app already buying downloads, the work starts with source quality and event checks. Campaign objectives and creative are revised around useful activity, so a low install cost does not hide a high cost per customer.
Return usage recovery
For an app with an installed audience but weak repeat use, the scope centres on permission-based onboarding and inactive-audience campaigns. Messages point to a specific action, such as completing a booking, rather than asking people to open the app without a reason.
What we do
The work we can include.
Each deliverable and the purpose it serves. Your written scope confirms what is included, who is responsible, and what it costs.
In-app event plan and tracking checks
A written event list names the actions that matter and how they are recorded through Firebase or a measurement partner. Test records show whether each agreed event reaches the measurement system and relevant ad account.
Google and Meta app campaigns
Campaign setup covers the agreed audience and budget, with an optimisation event suited to the available tracking. You review the campaign objective and spending limits before launch.
App campaign creative
Ad copy and creative show the app's actual purpose, such as booking a service or placing a repeat order. Approval copies let you check the offer against what the live app delivers.
Store and destination checks
An alignment check compares the ad with the store listing and arrival screen. Deep links to relevant app screens and custom store listings are included where supported and agreed, with test journeys checked before release.
Permission and onboarding messages
A message plan sets out when to request notification permission and what follows the first session. You review the wording and triggers for the agreed in-app, push, or WhatsApp messages, including opt-out handling.
Inactive audience campaigns
Agreed inactivity criteria define who receives a return message or remarketing ad. The audience rules and message destination are checked so people who have already completed the action are not chased unnecessarily.
App performance report
The report separates installs from useful activity and completed purchases where recorded. It states measurement gaps by operating system and compares cost per install with cost per agreed active customer.
How the result is measured
- Campaign clicks and installs by source, separate from completed actions
- Registrations and completion of the agreed activation event
- Return usage by install group and operating system
- Qualified enquiries and completed orders where recorded
- Response and opt-outs from re-engagement messages
- Cost per install compared with cost per active customer or recorded order
Recorded as a baseline before work starts, so every later report has an honest comparison.
Marketing and sales together
Your sales team needs the enquiry or order, not the download count.
Where the app captures enquiries, GullySales agrees which action creates a sales handoff and which existing record the salesperson receives. That record should carry the enquiry and available campaign source so sales can return its qualification or order status for comparison. For purchases completed inside the app, reporting uses the recorded purchase event; adding a new sales-system integration is separate work.
Decisions to make before the work starts
Developer access and release dependencies
Event setup and deep links depend on your app's existing tools and developer access. App code changes and release approvals remain dependencies, with responsibilities agreed before work starts.
Message permissions and review
Re-engagement depends on usable permission records and access to the chosen messaging tools. Your own compliance reviewer approves notices and regulated content; audiences without suitable permission are excluded.
Platform and production requirements
Android and iOS coverage, creative requirements, and the number of message journeys affect scope. Measurement or messaging tool charges are identified separately, and additional channels require written agreement.
This or a nearby service
Which piece of work fits your situation.
These services sit close to each other. The line between them, in plain words.
- Performance marketing and PPC
- Choose performance marketing and PPC when paid campaigns across search, social and display share one budget and promote a website or service. Choose mobile app marketing when the goal is installs and what people do inside the app afterwards, measured by app events.
- Meta advertising
- Choose Meta advertising when you want Facebook and Instagram campaigns for awareness, enquiries or website sales. Choose mobile app marketing when Meta is only one route to installs and the work also covers in-app events, return messages and inactive users.
- Customer onboarding
- Choose customer onboarding when a customer has already signed and needs a planned route to a first result with your business. Choose mobile app marketing when the problem sits earlier: bringing people to the app and encouraging a useful first action after installation.
A sample of the output
An in-app event plan says which actions count as success, and what each tells you.
This plan is for a clinic booking app. Read each row as an action inside the app, the moment it is recorded, and the question the team can answer once it is tracked reliably.
| In-app event | When it is recorded | Question it answers | Who acts on it |
|---|---|---|---|
| Account created | After the phone number is confirmed | Did the install turn into a usable account | Marketing, for campaign choice |
| Doctor profile viewed | When a profile page opens for a moment | Which specialities attract interest | Clinic manager |
| Appointment requested | When the booking form is submitted | Did the person reach the point of need | Front desk team |
| Reminder permission granted | When the person accepts message permission | Can the clinic send reminders the person agreed to | Marketing and clinic manager |
| Return visit after a gap | When the app opens again after a lapse | Is the app still useful after the first visit | Marketing, for inactive audience work |
Before we start
What we need from you.
The work depends on these. Each says why it is needed and what happens when it is missing.
- Developer access to the app
- Event tracking has to be placed in the app itself, so a developer must be available to add or check it. Contact details and a test build are acceptable. Without developer time, installs are counted but actions inside the app are not.
- Store listing and app links that work
- Campaigns send people to your Android or iOS store pages, so the listing must be live and accurate. Draft text is acceptable if it is approved before launch. Without a working link, paid clicks end on an error.
- A written meaning of a good user
- Installs alone say little. You decide which action marks a useful user, such as a booking or a first order. Without that definition, reporting defaults to downloads and the campaign is judged on the weakest measure.
- A message permission and consent record
- Return messages go only to people who agreed to receive them. A consent flow in the app, with its wording, must exist. Without it, messaging stays switched off for everyone, inactive users cannot be reached, and the return-message part of the work has nothing to run on.
- Creative approval from one person
- Campaign images, short videos and store text need one approver. An owner or product lead suits. Without a single approver, assets wait between teams, wording changes after sign-off, and the campaign cannot move on to the journey test before launch.
How it works
How the mobile app marketing work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Success definition approval
You name the action worth paying to acquire and approve its definition. We record the available baseline for acquisition and return usage, along with enquiries or orders where the app captures them.
- 2
Tracking and development handoff
GullySales checks account links and event records. Missing app-side events or destination changes go to your developer, with campaign launch dependent on the agreed tests passing.
- 3
Campaign and message approval
You approve the audience and spend alongside the creative and message sequence. Your authorised reviewer signs off permission wording and any regulated claims before they are used.
- 4
Journey test and launch decision
The team checks the route from advertisement to store and into the app on the agreed devices. Campaigns launch once the destination and agreed measurement are working.
- 5
Performance review and changes
Results are compared by source and operating system against the baseline. We recommend campaign or message changes, while product faults go back to your app team; reporting frequency is agreed in writing.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Can you start before our app tracking is ready?
Does this include fixing the app or improving store rankings?
Will Android and iPhone results match exactly?
Can you send WhatsApp messages to everyone who installs?
Can you guarantee a cost per order?
How do we agree the budget and term?
By industry
Mobile app marketing, written for your industry.
Related services
Often bought with this, or instead of it.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.