Joined the community
03-10-2017
8:37:20 AM
Offline
Customize the badges you want to showcase on your profile
Re: Adobe Heartbeat : Understanding difference between Co...
MartinLegros
Level 1
2 likes
7 posts
0 solutions
Top badges earned
View profile
MartinLegros
- Adobe Analytics
107
0
0
Likes
Total Posts
Correct Reply
Thank you!
Views
Likes
Replies
Re: Adobe Heartbeat : Understanding difference between Content / Content Name (variable) / Video Name
MartinLegros
Level 1
2 likes
7 posts
0 solutions
Top badges earned
View profile
MartinLegros
- Adobe Analytics
108
0
0
Likes
Total Posts
Correct Reply
Hello Jayakrish, we have our own media player HTML5, and we are using
Heartbeat Javascript
Views
Likes
Replies
Adobe Heartbeat : Understanding difference between Content / Content Name (variable) / Video Name
MartinLegros
Level 1
2 likes
7 posts
0 solutions
Top badges earned
View profile
MartinLegros
- Adobe Analytics
192
0
4
Likes
Total Posts
Correct Reply
Hello everyone, Knowing that : "Content" is the value put in mediaID
(a.media.name)"Content Name (variable)" and "Video Name" are the value
put in "name" (a.media.friendlyName)"Content" and "Content Name
(variable)" are eVar, where as "Video Name" is a classification.My
question : Is "Video Name" a classification based on the eVar "Content"
or "Content Name (variable)" or another eVar? Thanks Martin
LegrosMontréal, Canada
Views
Likes
Replies
Re: Heartbeat and Custom Conversion - Expires after Visit / Hit
MartinLegros
Level 1
2 likes
7 posts
0 solutions
Top badges earned
View profile
MartinLegros
- Adobe Analytics
288
1
0
Likes
Total Posts
Correct Reply
Thanks a lot! I went with the processing rules solution!Martin Legros
Views
Like
Replies
Re: Heartbeat and Custom Conversion - Expires after Visit / Hit
MartinLegros
Level 1
2 likes
7 posts
0 solutions
Top badges earned
View profile
MartinLegros
- Adobe Analytics
149
0
0
Likes
Total Posts
Correct Reply
Hello Waqas,Thanks for the reply.Yes i am using Custom evars from Video
ContextData. The problem is that the solution is inside Native Apps that
are already released and I am receiving "no value" for some meta that
are not mandatory for each video. So the previous value persist for a
second video that has no value for the same evar.I was wondering if by
setting that evar to expire after HIT instead of Visit would be a
solution. (Solution #1)Another solution, would be to keep it to Expire
after V...
Views
Likes
Replies
Heartbeat and Custom Conversion - Expires after Visit / Hit
MartinLegros
Level 1
2 likes
7 posts
0 solutions
Top badges earned
View profile
MartinLegros
- Adobe Analytics
563
1
5
Likes
Total Posts
Correct Reply
Hello,For an Heartbeat implementation, if we use Custom Conversion
Variables, is it valid to set variable to expire after HIT instead of
VISIT?My hesitation is because there are multiple calls for one media
tracking (Start, aa_start, play every 10 seconds, complete), so I am not
sure if the "expire by HIT" is dangerous here?I have a feeling that it
is they only call sent to the SC server that is important for Custom
Variable, so it would be okay to use Expire by HIT. Would there be
problem with ...
Views
Like
Replies
(Hearteat) Can we change a Standard Video Metadata with processing rules
MartinLegros
Level 1
2 likes
7 posts
0 solutions
Top badges earned
View profile
MartinLegros
- Adobe Analytics
200
0
1
Likes
Total Posts
Correct Reply
Hello, With the trackSessionStart(), we can add Standard Video Metadata
and Custom Video Metadata.At the moment, we only use Custome Video
Metadata into our MobileApp. I was wondering if I can populate Standard
Video Metadata like SHOW or SEASON with processing rules like this one :
Overwrite value of : a.media.show(ContextData) with rc.nameoftheshow
(ContextData)Where rc.nameoftheshow is my Custom Context Data.It doesn't
seem to work.Thanks for your help. Martin
Views
Likes
Replies
