Alisyn Collins
アクティビティの概要
Alisyn Collinsさんの最近のアクティビティ-
Alisyn Collinsさんがコメントを作成しました: Hey Daniel, This sounds like an issue better suited to a ticket with our Support team. I suggest filing one with as much info as you can provide. One thing to definitely include is if it resolve...
-
Alisyn Collinsさんがコメントを作成しました: Hey Alex, This is an interesting ask. There's no specific data point "out-of-the-box" that is used to determine completion of a guide. However, if you assume that a completed guide means that the...
-
Alisyn Collinsさんがコメントを作成しました: Aldric Delahaie, yes indeed! You'd want to just add a filter operator just before the select like this: { "filter": "numEvents > 0"},{ "select": { "Event Count": "numEvents", "...
-
Alisyn Collinsさんがコメントを作成しました: Hi Graham, https://app.pendo.io/api/v1/metadata/schema/event contains event properties rather than metadata. It's the equivalent of what you'd see under Settings > Event Properties in the UI. ...
-
Alisyn Collinsさんがコメントを作成しました: Hi Mahesh, The not() selector is not supported for feature tagging. However, it should work for guide targeting.
-
Alisyn Collinsさんがコメントを作成しました: Hi Vivek, I've tried that script and it does work as expected against my test account. I was able to reproduce a 403 error by using an integration key without write access. Please double check th...
-
Alisyn Collinsさんがコメントを作成しました: Hey Brian, In general in the API responses? They are considered differently. And yes, depending on the field and your inputs, you may expect to see either null or an empty string returned.
-
Alisyn Collinsさんがコメントを作成しました: Hi Brian, Account ID can be set to null or an empty string to indicate that there is no account tied to a visitor for that event. However, trying to send null or an empty string for visitor ID wou...
-
Alisyn Collinsさんがコメントを作成しました: If you're looking specifically for page events, then you'd want to use the pageEvents source and an aggregation similar to this one below. The bulkExpand will take the visitors returned and pull a...
-
Alisyn Collinsさんがコメントを作成しました: 正式なコメントHi Shanal, There is currently no option to specify a specific apiKey to when sending client-side track events. Those events will be sent to both initialized keys.