Embed the player on your own site

Embedding is rolling out in stages; if you don’t see the Embed section, contact support.

Open Settings and scroll to the Embed section. Give the key a label (like “Our website”) and list the domains it’s allowed to run on, one per line — for example example.com.

The exact host you enter is allowed, and its www. equivalent is covered automatically. Subdomains are not implied — list blog.example.com separately if you need it too. Save, and copy the key it generates.

Open the event or recording you want to embed and go to its Embed player tab. Check the eligibility list — the recording needs to be ready, its quiz published, and video attached — then turn embedding on.

The same tab shows your ready-to-paste snippet, with your embed key and the course link already filled in. Paste it anywhere in your site’s HTML. A small loader script turns it into the player — no build step, no other setup.

The player is a fixed 16:9 rectangle, the same shape as a YouTube embed — give it the full width of your content column and it sizes its own height from that, so your page layout never shifts as a learner moves through the course.

Where can I paste it?

The snippet is plain HTML plus a <script>tag, so it works anywhere your site lets you add one. Where we’re not certain a plan or role allows it, we say so — check your plan if you’re not sure.

• WordPress (block editor) — add a Custom HTMLblock and paste the snippet in. You need a user role that’s allowed to add scripts — Administrator on most sites.
• WordPress (classic editor)— paste it in the Text tab, not the visual editor.
• Elementor — drop in an HTML widget and paste the snippet.
• Squarespace — paste it into a Code block. This needs the Business plan or above— check your plan.
• Wix — the Embed HTML element runs your code inside a sandboxed iframe, which is not supported yet. Link to the course on OpenCEU instead for now.
• Kajabi / Teachable— use the custom code block on the page or post you’re editing.
• Google Sites — not supported yet; it doesn’t allow custom<script> tags.

The link in your snippet goes to the best real page that exists for that recording, and we fill it in for you:

• Listed in the public catalog — it points at the course pagefor that recording. This is the one you want: a specific page about the specific talk on your visitor’s screen.
• Not listed — it points at your provider pageon OpenCEU instead. A recording you’ve kept out of the catalog has no public course page, so a link to one would be a dead end for anyone who clicked it.

If a recording isn’t listed, the Embed player tab says so and gives you a List this recording button. Listing it publishes the course page and upgrades the link; copy the snippet again afterwards to pick up the new one.

The line under the player reads Course by {your organization}· Powered by OpenCEU, and your organization’s name is a link to you — not to us. It’s your course; the credit says so on your own page, where your readers are.

By default it points at your website. You can do better than that:

• Fill in Credit link (optional) on the Embed player tab with a page about this specific talk— the event page, the write-up, the speaker’s page. A credit that lands somewhere relevant is worth far more than one that lands on a homepage.
• Leave it empty and we use your organization’s website. If you haven’t set one, the credit points at your OpenCEU provider page, so the line always works.

Don’t want it? Uncheck Credit the issuing providerabove the snippet before you copy it and the credit is left off that embed entirely. It’s your page — the “Powered by OpenCEU” badge stays, the credit is yours to drop.

Someone landing on your page sees the course — your organization’s name, your ACE provider number, the credit it awards, and one field: the email their certificate should go to, plus a Watchbutton. No account, no password, no popup, and no separate registration form — no OpenCEU account is needed to start. They type an email and press Watch, and the video plays right there on your page.

Behind the scenes that registers them, exactly as your registration form would — their name plus any custom questions you added to the event land on your registrant list — and the player runs the same attendance checks, the same no-fast-forward rule, and the same saved progress it always has. Someone who watches half a session on your site can finish it on openceu.com, or the other way round; it’s one record either way.

When they clear the last attendance check, a take the quiz button appears and the quiz opens right there in the player— the same quiz, the same 100% pass bar, the same required course rating.

Passing doesn’t issue anything on its own — the account is created (or matched) right here, at the certificate step, which is also where OpenCEU proves who the learner is before anything is issued in their name. We look up the email they typed at the start:

• No OpenCEU account yet— they fill in name, credential, state, role, and choose a password, right there in your page. That creates their account.
• Already has an OpenCEU account— they enter their OpenCEU password, or have a sign-in code emailed to them, without leaving your page.

Either way they then pick which certificate to take it as (BACB, or another body you’re approved for, or a general certificate of completion) and confirm the name that goes on it. That step issues the real certificate — numbered under your ACE provider number and emailed to them — and the player says so once it exists. The credential can’t be swapped afterwards, exactly as on OpenCEU. On a device or browser they’ve already proven themselves on, a returning learner just watches and claims — no repeat sign-in.

The one thing that happens on openceu.com is the download: the finished screen has a View certificate on OpenCEUbutton, because a certificate PDF is only ever served to someone signed in to OpenCEU. Everything before it — watching, attendance, the quiz, the rating, proving identity and earning the certificate — happens without your learner leaving your page.

Back on the Embed player tab, the Where this embed runs table lists every page we’ve seen load your embed, with a view count and a backlink status:

• Verified — the link is live and followed on that page.
• Unverified — we haven’t checked it yet.
• Missing or Nofollow — the link isn’t on the page, or it’s marked not to count. The player shows the in-player attribution bar to viewers on that page until it’s fixed.
• Unreachable — we couldn’t load the page to check it.

The Creditcolumn next to it is just information: a ✓ means we also found your “Course by” credit on that page, a – means we didn’t (or haven’t checked yet). It never changes your backlink status — that credit points at you, not at us, so whether it’s there is your call.

Click Re-check on a row any time after you fix something — you don’t have to wait for the weekly check to run again.