Cam dealer manifest_web_spec_v2.0_2014_04_08

Project Name: DWP Asset Distribution Software Application
Document Type: ADSA Dealer/ Provider Manifest Specification
Version: Version 2.0
Date: 2014-04-08
Author: Shift Digital
Reviewers: CPD
Document Owner: TMS/USA
Template Version: Version 0.4

ADSA Dealer/Provider Manifest Specifications Prepared by Sanctus, LLC DBA Shift Digital for TMS/USA
Version 2.0
TMS/USA Protected Page 2 of 21
Table of Contents
1.1 Revision History ........................................................................................................................................3
1.2 Reference Documents ...............................................................................................................................3
1.3 .........................................................................................................................................................................3
1. INTRODUCTION .............................................................................................................. 4
2. OVERVIEW...................................................................................................................... 4
3. CAM DISTRIBUTION MODEL............................................................................................ 4
3.1 Internal Process.........................................................................................................................................5
3.2 Publication ................................................................................................................................................5
3.3 Consumption.............................................................................................................................................6
3.4 Security.....................................................................................................................................................6
4. CAM PROVIDER MANIFEST ............................................................................................. 6
4.1 Provider Manifest .....................................................................................................................................6
4.2 CAM Provider Manifest XSD......................................................................................................................7
5. CAM DEALER MANIFEST.................................................................................................. 8
5.1 Dealer Manifest ........................................................................................................................................9
5.2 Manifest Hierarchy..................................................................................................................................14
5.2.1 CAMDealerManifest...................................................................................................................................14
5.2.2 CAMCampaign............................................................................................................................................14
5.2.3 CAMCreative ..............................................................................................................................................15
5.2.4 CAMCreativeSource ...................................................................................................................................15
5.2.5 CAMAsset...................................................................................................................................................15
5.2.5.1 Landing Pages (CAM VERSION 2.0)....................................................................................................15
5.3 CAM Dealer Manifest XDS.......................................................................................................................16
6. ASSET TRACKING SUPPORT........................................................................................... 20
7. INTEGRATION SUPPORT................................................................................................ 20
7.1 testing End point.....................................................................................................................................20
7.2 PRODUCTION END POINT........................................................................................................................20
8. SUMMARY.................................................................................................................... 21

Version 2.0
1.1 Revision History
1.2 Reference Documents
Name Date/Version Source
TDDS-DWP Asset Tracking Initiative (ATI) Technical Implementation Guide (TIG) 2/26/2013 TPG Consulting, LLC for TMS/USA
1.3
Num Description Date Status
001 Landing Pages 12/16/2013 IN PROGRESS
Date Version Authors Description
12/16/2013 V1.0 Shift Digital Initial release
04/08/2014 V2.0 Shift Digital Post Production 1.0 Update

Version 2.0
1. Introduction
This document contains the interface specification for the Toyota Digital Dealer Services (TDDS) Asset
Distribution Software Application.
This document is narrowly tailored toward the consumption of the Marketing Campaign Assets by the
Dealer and Dealer Provider entities that are participating in the Program. This document does not cover
any of the internal components or interfaces of the ADSA application, otherwise known as the CAM
project.
2. Overview
The Asset Distribution Software Application aka CAM for Campaign Asset Management, is part of
Toyota’s Dealer Web Site program. The application seeks to automate the assembly, collection and
dissemination of creative assets, used by the dealer community in carrying out various marketing
initiatives.
Prior to the CAM application, these assets were distributed in a number of different avenues including
email and FTP. Also, as the uses of the assets are varied, dealer and/or providers found it necessary to
recreate the creative in various sizes and configurations depending on their unique or special
presentation needs with varying levels of quality.
In order to effectively manage the creation and distribution of these assets in a way that does not
unduly burden the dealer and provider communities, and consistent with Toyota’s liberal approach in
supporting the unique needs of its dealer community, a solution was devised to allow the central
storage and generation of assets in a number of different permutations, while providing the required
flexibility to the consumers of the assets in the manner of their ultimate usage.
As these assets are required in highly available environments, the CAM solution was devised in such a
way, so that all assets are available using a content delivery network with its high availability and low
latency characteristics.
This document’s purpose is to describe the steps necessary to consume these assets using a Content
Delivery Network.
3. CAM Distribution Model
The CAM distribution model is based on a philosophy of providing the maximum flexibility to the dealer
community, while ensuring a high level of asset quality and standardization. It further seeks to provide
extremely high levels of availability, by using a world class content distribution network as its primary
method for the publish dissemination of related assets.
The following diagram may be helpful in describing this system’s asset distribution model.

Version 2.0
ADSA Publish Process
Dealer manifest and asset push are
synched
Akamai CDN Cloud Services
DWP Provider
DWP Dealer
Dealer
Manifest
XML File
Dealer
Manifest
XML File
Asset
Images, vides, ect
XML document describing all campaigns
and asset location on the CDN for a given dealer
All Assets are pushed to CDN
But not discoverable without
Dealer Manifest
Real-Time Access to Assets
From Dealer Web Sites
These assets are freely available on the CDN
but not discoverable as the URI must be known
to the party attempting to access the resource
Campaign Asset Links created based on Provider Standards
ADSA Campaign Management
Phase 1 : Unique URL for each Dealer
Phase 2: Dynamic Web Endpoint responding with location of
Dealer manifest file on the CDN
TMS Firewall
3.1 INTERNAL PROCESS
The two boxes below the red line, represent the internally housed and maintained Asset Distribution
Software Application (ADSA), otherwise known as CAM or Campaign Asset Management.
The original assets undergo several internal TMS processes and eventually are pushed to the publicly
available CDN by this process. The original asset creative are used to generate various permutations of
assets in different sizes and other image variables. Each permutation is optimized for a particular usage
scenario.
The CAM system, employs a standardized process for generating different versions of the same creative
with an eye towards quality and consistency of the assets in such a way as to guarantee the marketing
message and brand across all usage scenarios.
3.2 PUBLICATION
Once campaigns and their respective assets have been created, compiled and successfully passed quality
control, the CAM system publishes a unique XML file for each dealer, describing the campaigns and their
assets in a documented and published schema called the “CAM Dealer Manifest” file.
The DWP dealers and their Web Site Vendors or Providers, are then given the location of these Dealer
Manifest files, where the XML may be consumed. Some providers or dealers, may utilize their own

Version 2.0
content management systems where this file is parsed and the appropriate actions are taken by those
proprietary processes.
3.3 CONSUMPTION
In some scenarios, the assets may be accessed by the providers and either loaded into their own
systems, or loaded in by “reference”. Meaning they may want to simply load the URI for the asset into
their system and leave the body of the binary data on the CDN for access when necessary.
3.4 SECURITY
All campaign assets are classified as “public information”. They are currently being utilized on a number
of different web sites and are likely to have been proliferated on the web in many locations. While it is
true that all assets will be stored on a freely accessible CDN, it is first necessary to know the location of
the asset as no “browsing” support is offered by the CDN. That is to say, without the URI, one would be
hard pressed to be able to “find” the asset.
This is where the Dealer Manifest file comes into the picture. The location of the dealer manifest file is
currently static. However, during phase 2 of this project, a provider portal will be offered, where the
providers will need to utilize an endpoint for the dynamic discovery of this dealer manifest file. This
location will be changed for each publication process, ensuring that only authorized parties are able to
gain access to the manifest file, and as a result, to the underlying assets of each campaign.
4. CAM Provider Manifest
The Provider Manifest file is the starting point for each provider.
This XML file, located on Toyota’s publicly accessible CDN as a flat xml file, contains a path to where
assets for any of the dealer campaign may be located. In addition, it contains a link to each of the
provider’s dealer manifest files.
By consuming this schema, the provider may be able to locate their dealer’s campaign and the assets
required or available for each campaign.
4.1 PROVIDER MANIFEST
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CAMProviderManifest WebsiteVendorName="sample provider name" ProviderId="1"
Path="1-sample_provider_name"
ManifestURL="http://www.toyota.com/CAMPublic/p/1-sample_provider_name.xml"
ManifestId="4" AssetURL="http://www.toyota.com/CAMPublic/240ae5ac/">
<CAMDealerWrapper dateTime="2014-04-08T15:52:27.732-07:00" count="2">
<CAMDealers Path="42313-bc116741"
ManifestURL="http://www.toyota.com/CAMPublic/d/00001-bc116741.xml"
ManifestId="4" DealerName="Toyota of Any Town" DealerGuid="bc116741-b37b-11e3-
a345-ac162dbc18f8" DealerCode="00001"/>
<CAMDealers Path="12345-bc0982dd"
ManifestURL="http://www.toyota.com/CAMPublic/d/12345-bc0982dd.xml"

Version 2.0
ManifestId="4" DealerName="Toyota of Any Other Town" DealerGuid="bc0982dd-b37b-
11e3-a345-ac162dbc18f8" DealerCode="00002"/>
</CAMDealerWrapper></CAMProviderManifest>
In this example, the Provider has two dealerships. Toyota Of Any Town and Toyota of Any
Other Town with dealerCodes 00001 and 00002.
The location of each dealer’s manifest file is also provider as:
ManifestURL=http://www.toyota.com/CAMPublic/d/00001-bc116741.xml
ManifestURL=http://www.toyota.com/CAMPublic/d/12345-bc0982dd.xml
The location of all assets is also present in this file:
AssetURL=http://www.toyota.com/CAMPublic/240ae5ac/
Any asset references in the dealer manifest files, will be located below the above
reference point.
This allows the CAM system, to publish new assets in new locations, without impacting
existing assets. The system accomplishes this by creating a new asset folder each time a
publish event is generated on the internal system.
This causes all dealer manifest files to be re-written with new pointers to assets, while
leaving he existing assets available for providers who have not yet had an opportunity to
consume the new manifest files.
4.2 CAM PROVIDER MANIFEST XSD
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="CAMProviderManifest">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMDealerWrapper">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMDealers" maxOccurs="unbounded" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute type="xs:string" name="Path" use="optional"/>
<xs:attribute type="xs:anyURI" name="ManifestURL" use="optional"/>

Version 2.0
<xs:attribute type="xs:byte" name="ManifestId" use="optional"/>
<xs:attribute type="xs:string" name="DealerName" use="optional"/>
<xs:attribute type="xs:string" name="DealerGuid" use="optional"/>
<xs:attribute type="xs:int" name="DealerCode" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:dateTime" name="dateTime"/>
<xs:attribute type="xs:short" name="count"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:string" name="WebsiteVendorName"/>
<xs:attribute type="xs:short" name="ProviderId"/>
<xs:attribute type="xs:string" name="Path"/>
<xs:attribute type="xs:anyURI" name="ManifestURL"/>
<xs:attribute type="xs:byte" name="ManifestId"/>
<xs:attribute type="xs:anyURI" name="AssetURL"/>
</xs:complexType>
</xs:element>
</xs:schema>
5. CAM Dealer Manifest
The Dealer Manifest file, offered as an XML flat file sitting on a predefined location for each dealer,
contains all of the necessary information a dealer may need, in order to decide which campaign to
display on its site at any given time. This manifest file, also contains links to all of the required assets for
a given campaign at a given point in time.
By consuming this manifest file, the dealer is able to place the “right” campaign with the “right” asset on
the page at any given time.
The CAMCampains node may contain 0 to (n) CAMCampaign Elements for a given dealer. As this XML is
based on a single Dealer, only the campaigns are appropriate for that dealer are included. No all
campaigns are included in the dealer’s manifest file.

Version 2.0
Also not all campaigns included should be always shown. The Provider and/or Dealer are responsible
to apply the following business rules;
The start date and end date of each campaign need to be compared with current time in order to
determine if
1. Is the campaign expired?
2. Is this a future campaign or one that needs to be shown sometime in the future?
The dynamic application of time sensitive rules allow the publishing of assets to occur prior to when
they are to be displayed by each dealer and also, allows for the instantaneous termination of campaign
displays, without the need for a synchronize file publish event.
You may expect to see campaigns that have start dates of up to 7 to 14 days in the future. Also, there
may be campaigns present in the xml file that have an end date of 7 to 14 days in the past.
Within the CAMCampaign element there may exists one or more CAMCreatives with each representing
a unique marketing message that implies tracking and model applicability. However no physical asset is
associated at this level as each “Creative” may have multiple visual manifestations.
These are called CAMCreativeSource that represent a unique original art work submitted by creative
agencies.
In turn, each CAMCreativeSource may have (n) number of various derivative works, generated for a
specific visual Use Case. These are the different sizes of the same image, represented by the parent
CAMCreativeSource and part of the same marketing message as represented by CAMCreative.
Therefore, the campaign assets are contained in the CAMAsset node.
In order to find the asset on the CDN the following logic may be utilized.
AssetURL = CAMDealerManifest.AssetURL + CAMAsset.Path + CAMAsset.Name
These assets are normalized across all campaigns, the same asset URL may be utilize for different
campaigns.
Also no code should be written to assume the presence of assets in different sized based on the pattern
detected in the uniform way in which they are stored.
Only assets that have a reference in manifest files, are guaranteed to exist.
5.1 DEALER MANIFEST
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CAMDealerManifest WebsiteVendorName="SomeProvider.com" ProviderId="1000" Path="1007-
1bf89991" ManifestURL="http://localhost:8080/CAMPublic/d/1007-1bf89991.xml"
ManifestId="2" DealerName="Bill Penney Toyota" DealerGuid="1bf89991-bc43-11e3-b94c-
00059a3c7a00" DealerCode="1007" AssetURL="http://localhost:8080/CAMPublic/f671b247/">
<CAMCampaigns dateTime="2014-04-08T16:48:15.218-07:00" count="1">

Version 2.0
<CAMCampaign startDate="2014-04-08T16:47:20-07:00" required="false" priority="0"
name="May Sales Event Test" ManifestId="2" id="1" groupName="May Sales Event"
geography="National" endDate="2014-07-07T16:47:20-07:00">
<CAMCreative Required="false" MonthYear="05-2014" Model="All Models"
ImageSearchTerms="Camry Toyota Sedan" ImageAltText="Camry Alt Text" Name="Camry Creative"
Id="1" SubGroup="Ladera">
<CAMCreativeSource MediaBinFileName="06-13_01_cat-everything-you-
want_990x557_0000000196_camry_r_xta.jpg" MediaBinAssetId="8FFA2EE0-F37B-4C8A-9C1E-
F277866C86F8" Width="990" Height="557" CAMAssetCount="3">
<CAMAsset Width="712" Path="May-Sales-EventLaderaCamry-Creative712380"
Name="05-14_TY_May-Sales-Event-Ladera_712x380_5_All-Models_O_xta.jpg" Id="13"
Height="380">
<CAMTracking>
<SiteCatalyst version="1.0">
<Click tmsomni.products=";05-14_TY_May-Sales-Event-Ladera_712x380_5_All-
Models_O_xta;;;event28=1" tmsomni.events="event28"/>
<Impression tmsomni.products=";05-14_TY_May-Sales-Event-
Ladera_712x380_5_All-
Models_O_xta;;event29=1;evar43=img|evar61=all|evar54=o|evar49={$CAM_PAGE_POSITION}"
tmsomni.events="event29"/>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="256">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="272">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
</CAMCreativeSource>
want_960x301_0000000196_camry_r_xta.jpg" MediaBinAssetId="53EE2EAE-4072-4DEF-B3BE-
640D40963F58" Width="960" Height="300" CAMAssetCount="3">

Version 2.0
Height="380">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="256">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="272">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
want_960x300_0000000196_camry_r_xta.jpg" MediaBinAssetId="23BE0825-2C47-4405-AAEE-
3FF80A361A2F" Width="960" Height="300" CAMAssetCount="3">
Height="256">
<CAMTracking>

Version 2.0
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="380">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="272">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
want_728x90_0000000196_camry_r_xta.jpg" MediaBinAssetId="9681C41E-F1F2-41A6-AAE1-
79D3565CA337" Width="728" Height="90" CAMAssetCount="3">
Height="272">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="300">
<CAMTracking>

Version 2.0
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="282">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
want_1024x320_0000000196_camry_r_xta.jpg" MediaBinAssetId="75B5BA2A-3447-44B3-A63D-
5881882B89B2" Width="1024" Height="320" CAMAssetCount="3">
Height="272">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
Height="256">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>

Version 2.0
Height="380">
<CAMTracking>
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
</CAMCreative>
</CAMCampaign>
</CAMCampaigns>
</CAMDealerManifest>
5.2 MANIFEST HIERARCHY
The dealer manifest schema contains the following elements in a hierarchical organization;
 CAMDealerManifest
o CAMCampaign
 CAMCreative
 CAMCreativeSource
o CAMAsset
 CAMTracking
 SiteCatalyst
5.2.1 CAMDealerManifest
This element contains attributes about the Dealer including identifying information and unique
identifier. All other elements will appear inside or under this element.
5.2.2 CAMCampaign
This entity contains the attributes about a specific campaign. The name of the campaign as well as its
start and end dates are contained here. Its group name will denote the marketing effort of which this
campaign is a part. The Geography attribute will show the campaign’s applicability to a specific TDA,
Region or Division without TMS’s dealer organization hierarchy. Campaigns that are not applicable for a
given dealer, WILL NOT be present in the dealer manifest file. The geography attributes are here as a
confirmation, rather than a selection criteria.

Version 2.0
5.2.3 CAMCreative
A creative is simply a logical entity describing a marketing message within a campaign. This is the “idea”
or “message” behind the marketing artifact. This could represent a picture of a Tundra puling a space
shuttle or another concept. Attributes such as if the creative is “required” or not, or what product model
it may apply to are provided at this level and without regard to an actual asset. This is the “logical”
portion of the creative and represents the conceptual set of attributes for the creative, applied to all
assets under this creative.
5.2.4 CAMCreativeSource
The Creative Source represents the original art work or actual creative that TMS has acquired from its
marketing resources. A single Creative or concept, may contain multiple original assets, authored for
different purposes or usage scenarios. These are not auto generated permutations of images, but actual
original creative sources upon which all permutations are based.
5.2.5 CAMAsset
This element represents actual assets that may be consumed. All occurrences of this element represent
different versions of the same CreativeSource and contain identical images or content, but in different
size and physical dimensions intended to satisfy as may different presentation scenarios as dealers and
providers are likely to encounter in their own unique presentation scenarios.
In addition to size and other attributes, the exact location of the asset’s corpus is define at this level,
allowing the consumer of the dealer manifest schema to find and retrieve the actual asset contents
either directly during the page view process, or in advance as part of a store and forward consumption
scenario.
5.2.5.1 Landing Pages (CAM VERSION 2.0)
A unique type of asset called landing pages will be support. However, the details of this asset structure
are still under designs and development. But the focus of the design at the present time is to define a
standard format ZIP file, containing a fixed structure inside which assets and/or links to assets are
organized in such a fashion that the consumer of this system, will be able to utilize them in accordance
with their own requirements.
The following structure is under development at the current time:
index.xml
pages
{pages1……n}
assets
images{assets1……n}
The above standard format zip file, will also be place on the CDN for easy access. The CAMAsset element
will be appropriately attributed and the path defined to point to the location on the CDN in a similar
manner to all other assets. However, this type of asset, represent an encapsulation of web elements
that are meaningful together and as part of a single logical asset or if you will, a “mini site”.

Version 2.0
5.3 CAM DEALER MANIFEST XDS
The following XDS defines the CAM Dealer Manifest Schema.
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="CAMDealerManifest">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMCampaigns">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMCampaign">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMCreative">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMCreativeSource" maxOccurs="unbounded" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMAsset" maxOccurs="unbounded" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="CAMTracking">
<xs:complexType>
<xs:sequence>
<xs:element name="SiteCatalyst">
<xs:complexType>
<xs:sequence>
<xs:element name="Click">
<xs:complexType>
<xs:simpleContent>

Version 2.0
<xs:attribute type="xs:string" name="tmsomni.products"
use="optional"/>
<xs:attribute type="xs:string" name="tmsomni.events"
use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="Impression">
<xs:complexType>
<xs:simpleContent>
<xs:attribute type="xs:string" name="tmsomni.products"
use="optional"/>
<xs:attribute type="xs:string" name="tmsomni.events"
use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:float" name="version" use="optional"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:short" name="Width" use="optional"/>
<xs:attribute type="xs:string" name="Path" use="optional"/>
<xs:attribute type="xs:string" name="Name" use="optional"/>
<xs:attribute type="xs:byte" name="Id" use="optional"/>
<xs:attribute type="xs:short" name="Height" use="optional"/>

Version 2.0
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:string" name="MediaBinFileName" use="optional"/>
<xs:attribute type="xs:string" name="MediaBinAssetId" use="optional"/>
<xs:attribute type="xs:short" name="Width" use="optional"/>
<xs:attribute type="xs:short" name="Height" use="optional"/>
<xs:attribute type="xs:byte" name="CAMAssetCount" use="optional"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:string" name="Required"/>
<xs:attribute type="xs:string" name="MonthYear"/>
<xs:attribute type="xs:string" name="Model"/>
<xs:attribute type="xs:string" name="ImageSearchTerms"/>
<xs:attribute type="xs:string" name="ImageAltText"/>
<xs:attribute type="xs:string" name="Name"/>
<xs:attribute type="xs:byte" name="Id"/>
<xs:attribute type="xs:string" name="SubGroup"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:dateTime" name="startDate"/>
<xs:attribute type="xs:string" name="required"/>
<xs:attribute type="xs:byte" name="priority"/>
<xs:attribute type="xs:string" name="name"/>
<xs:attribute type="xs:byte" name="id"/>
<xs:attribute type="xs:string" name="groupName"/>
<xs:attribute type="xs:string" name="geography"/>
<xs:attribute type="xs:dateTime" name="endDate"/>
</xs:complexType>

Version 2.0
</xs:element>
</xs:sequence>
<xs:attribute type="xs:dateTime" name="dateTime"/>
<xs:attribute type="xs:byte" name="count"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute type="xs:string" name="WebsiteVendorName"/>
<xs:attribute type="xs:short" name="ProviderId"/>
<xs:attribute type="xs:string" name="Path"/>
<xs:attribute type="xs:anyURI" name="ManifestURL"/>
<xs:attribute type="xs:string" name="DealerName"/>
<xs:attribute type="xs:string" name="DealerGuid"/>
<xs:attribute type="xs:short" name="DealerCode"/>
<xs:attribute type="xs:anyURI" name="AssetURL"/>
</xs:complexType>
</xs:element>
</xs:schema>
When a dealer manifest file is updated by the CAM publishing process, the asset links contains in the
manifest file will of course be already out there and available on the CDN. Moreover, assets defined in
the prior version of the manifest file will also continue to be available on the CDN, but may no longer be
referenced by the latest dealer manifest file.
The CAM system will likely retire assets that are no longer reference by any manifest file in the
subsequent dealer manifest revision or by the lapse of a certain amount of time.
Assets not referenced by any dealer manifest file will lapse and no longer be available on the CDN after
30 days.
The consumers of this system, are advised to put in place automated processes that refresh and
update their internal information or links to assets at least once every week or they risk pointing
viewers to assets on the CDN that may no longer be available.
The above warning is only applicable to those providers and/or dealers who have selected to serve up
URL for assets directly against the CDN. In the case where assets are copied to another location for real
time consumption, obviously those copies are not impacted by the clearing on the CDN resources after

Version 2.0
they are removed. In this case, they risk not being in compliance with marketing covenant, as they
would be presenting consumers with outdated assets and/or campaigns.
6. Asset Tracking Support
The Dealer Manifest Schema contains additional elements that facilitate the tracking of assets in
accordance with the provisions of the TDDS-DWP Asset Tracking Initiative (ATI).
Each asset is annotated by a CAMTracking Element containing the tracking provider specifics.
In the example below, an asset for a Camry is being tagged with the appropriate Site Catalyst values
required for the Click and Image events.
<CAMAsset Width="712" Path="May-Sales-EventLaderaCamry-Creative712380" Name="05-
14_TY_May-Sales-Event-Ladera_712x380_4_All-Models_O_xta.jpg" Id="10" Height="380">
<CAMTracking>
<Impression tmsomni.products=";05-14_TY_May-Sales-Event-Ladera_712x380_4_All-
</SiteCatalyst>
</CAMTracking>
</CAMAsset>
These values are generated by the CAM system automatically, and remove a great deal of potential for
errors inherent in the tagging process and therefore, all Dealers and Providers are encouraged to take
advantage on this feature.
7. Integration Support
The CAM project maintains a separate environment for its ongoing Development, Testing and
Production.
Parties intending on integrating with this system are encouraged to access the following location to
retrieve the dealer manifest xml file.
Each provider will be given a specific URI relative to the location below from which they may retrieve
their own Provider Manifest. Please contact the DWP program representatives for your unique URI.
7.1 TESTING END POINT
http://staging.toyota.com/CAMPublic
The dealer manifest file retrieved from this end point, will contain asset links that are also part of the
Testing environment.
Production code should not utilize any resources gained from this environment as these are not
guaranteed to exist and may be revised without notice.
7.2 PRODUCTION END POINT

Version 2.0
http://www.toyota.com/CAMPublic
The production endpoint will contain the most recent dealer manifest file for any given dealer.
All links to assets will be links to the production CDN distribution and will be immutable for at least one
generation of dealer asset manifest revisions.
When a dealer manifest file is updated by the CAM publishing process, the asset links contains in the
manifest file will of course be already out there and available on the CDN. Moreover, assets defined in
the prior version of the manifest file will also continue to be available on the CDN, but may no longer be
referenced by the latest dealer manifest file.
The CAM system will likely retire assets that are no longer reference by any manifest file in the
subsequent dealer manifest revision or by the lapse of a certain amount of time.
Assets not referenced by any dealer manifest file will lapse and no longer be available on the CDN after
approximately 30 days or 3 publishing generations, whichever comes first.
The consumers of this system, are advised to put in place automated processes that refresh and update
their internal information or links to assets at least once every 7 days or they risk pointing viewers to
assets on the CDN that may no longer be available.
The above warning is only applicable to those providers and/or dealers who have selected to serve up
URIs for assets directly against the CDN. In the case where assets are copied to another location for real
time consumption, obviously those copies are not impacted by the clearing on the CDN resources. In
this case, they risk not being in compliance with marketing covenant, as they would be presenting
consumers with outdated assets and/or campaigns.
8. Summary
The Asset Distribution Software Application or (CAM) represent a major advancement in the manner in
which creative assets are made available to the Toyota Dealer Community. By leveraging industry
standard methods and technologies such as HTTP, XML and CDN, the CAM application enables the
dealer community to provide a consistent marketing message with the least manual effort on the part of
the dealers and their vendors.
Constructive feedback is always welcome.

Cam dealer manifest_web_spec_v2.0_2014_04_08

Recommended

Recommended

More Related Content

Similar to Cam dealer manifest_web_spec_v2.0_2014_04_08

Similar to Cam dealer manifest_web_spec_v2.0_2014_04_08 (20)

Recently uploaded

Recently uploaded (20)

Cam dealer manifest_web_spec_v2.0_2014_04_08