DEMO SUPPLY / THE PUBLISHER’S RESEARCH DESKPERMISSION · COVERAGE · DELIVERY
Demo SupplySourcing research for US-facing publishers
Scope a shortlist

06 Section 06 of 12 / Hear the perspectives

Expert Q&A

Ask experts the questions that could change a sourcing decision.

23Research pages
60Sources cited
28 Oct 2026Last updated
A document folio and game cards connected by a pink permission tab

Interview agenda

Better questions before a buying decision.

Proposed interviews, not completed conversations. No answers or endorsements are attributed to the proposed experts.

01

What written permission would make you comfortable approving a demo-slot launch?

Explore the question →
02

Does a casino aggregator agreement actually cover independent publisher demo embedding?

Explore the question →
03

What does ‘available in the United States’ mean in your proposal?

Explore the question →
04

How many games remain useful after rights, relevance and availability checks?

Explore the question →
05

When comparing a demo slot API with an iframe, which jobs does each actually perform?

Explore the question →
06

What must publishers change before the documented 15 November 2026 signing deadline?

Explore the question →
07

How do you prove a slot demo is ready to play rather than merely loaded into a frame?

Explore the question →
08

When a slot demo iframe fails on mobile Safari, how do you distinguish the causes?

Explore the question →
09

What would a credible mobile demo integration pilot test—and what would it not prove?

Explore the question →
10

What metadata may we publish, and how will corrections reach our editorial pages?

Explore the question →
11

How can an editor know whether the demo matches the game being reviewed?

Explore the question →
12

What does the embedded game collect, and can the publisher enforce visitors’ privacy choices?

Explore the question →
13

What audience and age controls are appropriate for this particular publisher?

Explore the question →
14

Who controls the promotions inside and around the demo?

Explore the question →
15

When is free authorised studio access better value than paid aggregation?

Explore the question →
16

What does your support promise cover when the studio’s endpoint fails?

Explore the question →
17

If the supplier disappears or a studio withdraws, what can we keep and how would we recover?

Explore the question →
18

What evidence would make you approve, narrow or reject this purchase?

Explore the question →

In this section

01

What should a buyer learn from these interviews?

Whether a proposed demo-content arrangement is authorised for the intended use, technically dependable and worth its full operating cost.

Read →
02

Which developments make the questions timely?

Three documented developments deserve specific attention in supplier conversations:

Read →
03

Which recognised experts should the desk approach?

Build a panel around complementary expertise, then add the people who actually own the proposed contract and integration.

Read →
04

1. What written permission would make you comfortable approving a demo-slot launch?

Interview objective: Obtain a usable permissions checklist, not a generic assurance that the games are public or free.

Read →
05

2. Does a casino aggregator agreement actually cover independent publisher demo embedding?

Interview objective: Establish the downstream grant rather than infer it from studio relationships or operator deployments.

Read →
06

3. What does ‘available in the United States’ mean in your proposal?

Interview objective: Separate contractual territory, observed access and the legality of surrounding promotions.

Read →
07

4. How many games remain useful after rights, relevance and availability checks?

Interview objective: Replace advertised catalogue size with a reproducible measure of usable coverage.

Read →
08

5. When comparing a demo slot API with an iframe, which jobs does each actually perform?

Interview objective: Obtain an architecture diagram that separates catalogue synchronisation from visitor-facing game delivery.

Read →
09

6. What must publishers change before the documented 15 November 2026 signing deadline?

Interview objective: Turn a supplier-specific migration notice into a verifiable release plan.

Read →
10

7. How do you prove a slot demo is ready to play rather than merely loaded into a frame?

Interview objective: Agree a measurable game-ready event and an honest treatment of missing instrumentation.

Read →
11

8. When a slot demo iframe fails on mobile Safari, how do you distinguish the causes?

Interview objective: Produce a diagnosis tree rather than a blanket instruction to disable browser protections.

Read →
12

9. What would a credible mobile demo integration pilot test—and what would it not prove?

Interview objective: Agree acceptance criteria before procurement, without presenting a small sample as nationwide assurance.

Read →
13

10. What metadata may we publish, and how will corrections reach our editorial pages?

Interview objective: Establish both data-use rights and an operational correction workflow.

Read →
14

11. How can an editor know whether the demo matches the game being reviewed?

Interview objective: Obtain configuration evidence rather than accept matching artwork or a shared title as sufficient.

Read →
15

12. What does the embedded game collect, and can the publisher enforce visitors’ privacy choices?

Interview objective: Connect contractual data descriptions with observable browser behaviour.

Read →
16

13. What audience and age controls are appropriate for this particular publisher?

Interview objective: Avoid treating a generic age label as a substitute for an audience assessment.

Read →
17

14. Who controls the promotions inside and around the demo?

Interview objective: Establish responsibility for the complete visitor experience, not only the publisher’s surrounding text.

Read →
18

15. When is free authorised studio access better value than paid aggregation?

Interview objective: Compare complete operating models rather than headline subscription prices.

Read →
19

16. What does your support promise cover when the studio’s endpoint fails?

Interview objective: Translate ‘monitoring’ and ‘priority support’ into accountable service terms.

Read →
20

17. If the supplier disappears or a studio withdraws, what can we keep and how would we recover?

Interview objective: Establish contractual exit rights and genuine dependency separation before renewal.

Read →
21

18. What evidence would make you approve, narrow or reject this purchase?

Interview objective: End with an explicit decision rule rather than a collection of interesting opinions.

Read →
22

How should the desk run and publish the interviews?

Request an example, an artefact and a boundary for every important answer.

Read →

Desk self-assessment / out of 10

9Buyer fit
9Depth
9Search relevance
8Sources