Google Maps & Reviews
Directions, place details and the merchant’s review request link.
A configurable NFC journey for stores that want more useful discovery, conversation and social touchpoints—without asking customers to download another app.
Concept demonstration. Destination availability and reporting depth depend on the agreed pilot scope and platform rules.
Counter → tap → destination
Physical visit → digital next step
Place a managed NFC touchpoint where intent is highest: checkout, reception, the table, the room, the fitting area or the exit. The customer sees a focused journey—not a wall of unrelated links.
Open a lightweight mobile journey first.
Update the agreed store route as campaigns and markets change.
Reviews, follows and messages are completed inside the destination platform.
Destination framework
Broad-access destinations launch faster as standard links. OAuth and publishing APIs are scoped separately because approval, account type and market availability vary by provider.
Directions, place details and the merchant’s review request link.
Start a store conversation with a prepared message.
Open the store profile, a campaign post or a Reel.
Guide customers to a profile, video or approved campaign destination.
Open a channel, Shorts feed or store story.
Add destinations that match the store category and target market. Deep platform APIs are only included after scope and approval checks.
The tap route
The visitor touches an NFC plaque or scans the fallback QR.
The mobile journey presents store and market-appropriate actions.
The customer opens and completes the selected action on the platform.
The store reviews journey opens and destination clicks under DGP control.
Product preview
These product visuals show the intended pilot experience. Final destinations, language and reporting are configured during scope confirmation.
Open full view ↗
Open full view ↗
Open full view ↗
Built around the physical moment
A pilot starts with the customer moments that matter for that business, not a generic list of social icons.
Review, return directions, menu story, WhatsApp reservation.
New arrivals, social profile, product education, client chat.
Guest information, travel reviews, maps and short-form stories.
Directions, consultation, channel content and follow-up entry.
What the pilot does—and does not do
Global pilot intake
Share the market, store count and customer actions you want to improve. DGP will review fit, platform constraints and a pilot scope before any price or payment commitment.
Fit reviewStore type, markets and current destinations
Scope proposalTouchpoints, pages, reporting and rollout boundaries
Written orderPrice, currency, timing and acceptance criteria
Submitting this request does not create a paid order. Overseas payment options, currency, fees and delivery terms are confirmed in writing after scope review.
Pilot questions
No. The link-first pilot opens a mobile web journey and then hands the customer to the selected destination. The destination platform may still require its own app or account for actions such as posting a review.
Yes. A DGP-managed destination can be configured by store, campaign and agreed market rules without rewriting the physical tag. Market routing is confirmed during pilot scoping.
No. Customers choose the destination and complete any review, follow, message or publishing action inside the destination platform. DGP does not automate customer consent.
The proposed reporting layer records events under DGP control, such as NFC journey opens and destination clicks. Completion inside a third-party platform is only reported when an approved integration provides reliable confirmation.