3rd party data explorer

A method, comprising:

• extracting, by a processing circuit, an identifier from first third party activity data, wherein the identifier is extracted based at least in part on routing information of a traffic packet of the first third party activity data;
• determining, by the processing circuit, an item of an entity profile based at least in part on the identifier;
• based on the item, determining, by the processing circuit, a computing entity external to the processing circuit associated with the first third party activity data and the identifier, wherein the computing entity comprises at least one entity device associated with a third party entity and is determined by assigning the first third party activity data to the at least one entity device by matching at least one unique identifier comprised in the first third party activity data to the entity profile associated with the third party entity, the at least one unique identifier uniquely identifying the at least one entity device among a plurality of entity devices;
• and
• monitoring, by the processing circuit, third party activity on a plurality of data channels associated with the computing entity, comprising collecting second third party activity data, wherein collecting the second third party activity data comprise querying or accessing the plurality of data channels.

One or more non-transitory computer readable media storing instructions that, when executed by a processor, causes the processor to:

• extract an identifier from first third party activity data, wherein the identifier is extracted based at least in part on routing information of a traffic packet of the first third party activity data;
• determine an item of an entity profile based at least in part on the identifier;
• based on the item, determine a computing entity external to the processor associated with the first third party activity data and the identifier, wherein the computing entity comprises at least one entity device associated with a third party entity and is determined by assigning the first third party activity data to the at least one entity device by matching at least one unique identifier comprised in the first third party activity data to the entity profile associated with the third party entity, the at least one unique identifier uniquely identifying the at least one entity device among a plurality of entity devices;
• and
• monitor third party activity on a plurality of data channels associated with the computing entity, comprising collecting second third party activity data, wherein collecting the second third party activity data comprise querying or accessing the plurality of data channels.