Audio Trigger Pay-as-you-go Plan

Every trigger event, a measurable result.

Turn every "audio moment" in CMs, in-store BGM, and event sound into a confirmed action — coupon claims, lottery entries, in-store visits, and more.

The Audio Trigger Pay-as-you-go Plan is a marketing platform that counts every single touch, from reach to conversion.

A new concept — 1 hands-on demo makes it click. Your phone's mic picks up the sound and reacts.

Pricing

A simple pay-per-trigger model. Purchase in 10,000-trigger units. Trigger count resets monthly.

What is the Audio Trigger Pay-as-you-go Plan?

A model where "trigger count = number of confirmed actions" maps directly to marketing KPIs. ROI per campaign or channel is measured by actual trigger detections and action completions, and pricing scales with usage.

Trigger count = actual reach

Number of users who actually heard and reacted to the audio — counted as real numbers, not estimated impressions.

Action completions = confirmed CV

Measure how many users completed your designed action — lottery entries, coupon claims, in-store points, and more.

Pricing scales with results

Pay-as-you-go model tied to trigger count means no wasted ad spend.

How it works

Embed a trigger in your broadcast or in-venue audio. The moment a user's smartphone detects it, your pre-configured confirmed action fires — lottery, coupon issuance, landing-page navigation, etc. All trigger and completion counts are tracked on the dashboard.

1

Prepare the trigger audio

Choose fingerprint mode (register existing audio as-is, no modification needed) or watermark mode (embed an inaudible signal). Any CM, signage BGM, or event sound can become a trigger — with or without source modification.

2

Capture by smartphone mic

If users have your campaign page open in any web browser, the trigger fires the moment they hear the audio. No app required.

3

Action confirmed

Lottery entry, coupon claim, code issue, or LP navigation — your designed action runs automatically and is recorded.

4

Count & measure

Detection counts, action completions, and code-redemption stats visualize in the dashboard — evaluable per campaign or channel.

Use cases

The Pay-as-you-go Plan converts "watch / dwell / experience" into "confirmed actions" across any audio environment.

📺

CM / TV-sync campaigns

Air during broadcastSmartphone detectionCode / lottery entry

Embed triggers in 15- or 30-second CM slots and turn viewers into actors. Count how many viewers actually engaged — as real numbers.

🏟️

Event-venue lottery / distribution

In-venue audioVisitor smartphone detectionOn-site lottery / prize pickup

At a pro-baseball game, audio triggers fired a smartphone lottery and winners collected prizes inside the stadium — a complete reach-to-fulfillment funnel.

🏪

Store & signage sync

Store BGM / signageVisitor smartphone detectionCoupon / loyalty points

Embed triggers in store BGM or digital signage so only customers actually present in the store receive coupons or rewards.

Track record (selected metrics)

Selected metrics from real deployments across broadcast, theater, stadium, and large-event use.

🎬 National theater promotion
Multi-million
Trigger detections (multi-week run)

During the theatrical release period across the country, smartphone audio triggers distributed limited-edition content to attendees — at a large, continuous scale.

⚾ Pro-sport single event
~17,000people
Lottery entrants (single-day event)

Stadium audio triggered an in-stadium lottery; winners collected prizes inside the venue — a complete single-event funnel.

🏀 Large-arena event
10,000+ scale
Simultaneous connections

"Smartphone penlight" experience deployed in a 10,000-person arena — stable under thousands of simultaneous connections.

* See the TOP page for more cases.

Measurable metrics

Reach → engagement → conversion, all measured as actual numbers. Drop straight into ad-effectiveness reports or ROI calculations.

Reach
Trigger detections

Number of users who actually heard and reacted to the audio. Real numbers, not GRP/impression estimates.

Engagement
Action completions

Users who completed your designed action — lottery entry, code claim, etc.

Conversion
Code redemptions / visits

Actual code usage or in-store prize collection — trackable to final CV.

Included management tools

Standard with the plan: a CMS for setup & operation and a real-time analytics dashboard. Designed for direct use by marketers and agency teams.

🛠

CMS (management console)

Link trigger audio to actions and run campaigns end-to-end.

  • Upload / register trigger audio and video
  • Map identifiers (meta) to actions
  • Manage reward images, coupons, redirect URLs
  • Campaign ON / OFF and scheduling
📊

Analytics dashboard

Real-time view from trigger reception to conversion — usable as-is for ad reporting.

  • Live counts of detections, completions, redemptions
  • Filter by campaign / channel / time
  • Time-window aggregation and CSV export
  • Reusable for agency reporting

* Live screens (CMS / Dashboard) are shown individually upon inquiry.

ROI estimate (rough guide)

Since only users who actually heard and reacted are billed, reach unit cost is extremely low — and CV unit cost typically lands an order of magnitude below traditional digital advertising.

Budget scenarios

Scale Trigger budget (ex-tax) Est. CV *1 Est. CPA
Small (pilot) JPY 30,000
10,000 triggers
1,000 – 3,000 JPY 10 – JPY 30
Medium (campaign) JPY 300,000+
100,000+ triggers (bulk discount applies)
10,000 – 30,000 JPY 10 – JPY 30
Large (nationwide) Contact us (bulk pricing)

CPA comparison with other ad channels (rough)

Channel Typical CPA range *2 Billing trigger
Search ads (CPC) JPY 500 – JPY 3,000 Click
Social ads (CPC) JPY 100 – JPY 500 Click
Video ads (CPV) JPY 10 – JPY 50 View start (VTR)
Audio Trigger Pay-as-you-go JPY 10 – JPY 30
Bulk discount lowers further
Real contact (audio detection)

*1 Estimated CV uses "action-completion rate 30 – 50%" and "final CV rate 10 – 30%" as reference. Actual numbers vary widely by campaign, channel, and experience design.

*2 Channel CPA ranges are industry averages for reference. Actual numbers depend on channel, industry, and delivery conditions.

Pre-launch technical requirements

Items that need to be decided at design / implementation, plus environmental prerequisites. Check internally with your team or agency before launch.

1. Delivery pattern

Fixed at production build:

  • Pattern A — Web-complete: reward image / coupon shown in browser.
  • Pattern B — App-integrated: WebView embed inside your existing app; identifier handed off to native.

2. Recognition methods (two options)

  • Audio fingerprint (EFP2): register existing audio as-is, recognize without modifying the source.
  • Audio watermark: embed an inaudible signal in your source for high-fidelity identifier control.

* Both methods can be combined.

3. Runtime requirements

  • HTTPS required (mic works only in a secure context)
  • WebAssembly-capable browser (current Chrome/Safari/Firefox/Edge)
  • User microphone permission required
  • Foreground only (stops in background / lock / call)
  • App integration: iOS 15.0+ / recent Android System WebView

4. Environmental notes

  • Recognition accuracy may drop in reverberant places (large halls, train stations)
  • Repeating audio patterns may require identifier design considerations
  • UI / flow for prompting mic permission significantly affects results

Getting started

From inquiry to launch in 4 steps.

  1. 1

    Inquiry

    We'll discuss your plan, trigger volume estimate, and use case.

  2. 2

    Sign up · CMS account issued

    After contracting, your CMS (management console) account is issued.

  3. 3

    Set up in CMS

    Register trigger audio, identifiers (meta), and delivery actions (coupons / images / URLs).

  4. 4

    Go live

    Start delivery as soon as setup completes. Monitor detection and completion in real time via the dashboard.

Contract & payment terms

Contract term

Monthly (1-month minimum). Auto-renews monthly; cancel by month-end.

Trigger usage

Purchased triggers must be used within the month. Unused balance expires at month-end with no carry-over.

Payment

Stripe online payment (credit card). Sign-up, payment, and operation all complete self-service.

Large-scale usage

For large-scale usage, please contact us for bulk discounts.

Music & audio rights

Acquisition and management of copyright, neighboring rights, and usage permissions for the music, audio, and content used as triggers are the sole responsibility of the customer. We disclaim all liability in this regard.

Privacy & data handling

The service uses the smartphone microphone. To eliminate user concerns, our data-handling policy is stated below.

🎙 Microphone usage

The mic only activates after explicit user permission via an opt-in flow following on-screen prompts. No audio is captured without permission.

📡 Recorded data handling

Microphone audio is used only to detect audio identifiers. The recording itself is never stored or transmitted; identifiers are extracted on-device, and only the identifier is sent to the server.

🔒 Personal information

The recognition layer alone does not collect any personally identifiable information. If your campaign collects PII (e.g., for coupon issuance), it is handled under your privacy policy.

FAQ

Does the user need to install an app?

No. Users simply open the campaign page in their smartphone's web browser — no app installation, no app-store review.

I'd like to try it at a small scale first.

You can start with the minimum 10,000 triggers (JPY 30,000 ex-tax). Monthly contracts let you validate effectiveness before scaling.

Can I cancel anytime?

The minimum term is one month, with monthly auto-renewal. Cancel by month-end to stop billing the following month.

Can it be embedded in our existing mobile app?

Yes. WebView integration into your existing app is supported. Please contact us for app integration details.

How is this different from other audio-recognition services?

Our parent company Evixar is Japan's No.1 acoustic communication technology vendor with 15+ years of broadcast and large-event production experience. Pricing is a simple pay-per-trigger model.

Will it work in noisy or echoey venues?

Recognition accuracy varies by environment. In reverberant places like train stations or large halls, the right recognition method (audio watermark / fingerprint) combined with identifier design can compensate.

Can I try it before launching in production?

You can confirm behavior via the demo shown at the consultation stage. Live operation starts from the minimum 10,000-trigger paid plan. Start small, validate, then scale up.