Skip to content

Fix typo and removed repeating line #442

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bpkmatthiasv wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Fix typo and removed repeating line #442

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
65caba5
Fix typo and removed repeating line
bpkmatthiasv Aug 8, 2024
a7fb3fc
Uppercase fix
bpkmatthiasv Aug 28, 2024
26b265b
Fix Initilaization typo
bpkmatthiasv Nov 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -646,7 +646,7 @@ SIMID supports nonlinear ads by providing a nonlinear specific API. Both linear

VAST supports nonlinear ads since version 2.0 including interactive ads that implement API frameworks.

VAST response describes nonlinear ads in the `<NonLinear>` node children. The `<NonLinear>` node attribute’s `apiFrmawork` value is `SIMID`. The node <IFrameResource> delivers a URI to the SIMID interactive component. The node `<AdParameters>` contains custom ad data for the creative’s consumption.
VAST response describes nonlinear ads in the `<NonLinear>` node children. The `<NonLinear>` node attribute’s `apiFramework` value is `SIMID`. The node <IFrameResource> delivers a URI to the SIMID interactive component. The node `<AdParameters>` contains custom ad data for the creative’s consumption.

<div class="example">
<div class="xml-highlight"><pre style="line-height: 125%">
Expand Down Expand Up @@ -1161,7 +1161,7 @@ The creative must respond to `Player:fatalError` with `resolve`. After `resolve`
See [[#workflow-error]]

### SIMID:Player:init ### {#simid-player-init}
The purpose of the `SIMID:player:init` message is to transport data to assist with the interactive component initialization. See [[#workflow-initialization]] and [[#workflow-uninterupted-initialization]].
The purpose of the `SIMID:Player:init` message is to transport data to assist with the interactive component initialization. See [[#workflow-initialization]] and [[#workflow-uninterupted-initialization]].

The creative must respond to `Player:init` with either [[#simid-player-init-resolve]] or [[#simid-player-init-reject]].

Expand Down Expand Up @@ -1522,7 +1522,7 @@ Note: In SIMID, the creative initializes the session and posts the first message

### SIMID:Creative:clickThru ### {#simid-creative-clickThru}

The `SIMID:Creative:clickThru` message notifies the player of a `clickthrough` for event tracking. SIMID delegates clickthrough execution to the creative, including redirecting the user to the landing page. The interactive component posts `clickThru` only when the creative classifies a user interaction as a clickthrough.
The `SIMID:Creative:clickThru` message notifies the player of a `clickthrough` for event tracking. SIMID delegates clickthrough execution to the creative, including redirecting the user to the landing page.

The interactive component posts the `Creative:clickThru` message only when the creative classifies a user interaction as a `clickthrough`. To open the landing page in the situations when user interaction does not constitute `clickthrough`, the creative must utilize [[#simid-creative-requestNavigation]] message.

Expand Down
Loading