Abstract: A system and method to manage data associated with a merchant system to provide in response to a search query from an end user system. The system and method to generate, in a data graph associated with a merchant system, a first entity type including a first data field storing a first data value corresponding to the merchant system. A second entity type comprising a second data field storing a second data value corresponding to the merchant system is generated in the data graph. A relationship type between the first entity type and the second entity type is established. A first update to the first data value of the first entity type is generated. In view of the relationship type, a second update to the second data value of the second entity type is generated. The first update of the first entity type and the second update of the second entity type are stored in the data graph.

Abstract: A system and method to manage data associated with a merchant system to provide in response to a search query from an end user system. The system and method to generate, in a data graph associated with a merchant system, a first entity type including a first data field storing a first data value corresponding to the merchant system. A second entity type comprising a second data field storing a second data value corresponding to the merchant system is generated in the data graph. A relationship type between the first entity type and the second entity type is established. A first update to the first data value of the first entity type is generated. In view of the relationship type, a second update to the second data value of the second entity type is generated. The first update of the first entity type and the second update of the second entity type are stored in the data graph.

Abstract: In one implementation, a method is provided that designates a first listing corresponding to a first web address as a representative listing of an entity. A provider system is searched to identify a second listing associated with the entity, wherein the second listing corresponds to a second web address. A determination is made that the second listing satisfies matching criteria associated with the first listing. An instruction to suppress the second listing on the provider system is received from a system associated with the entity. A request to suppress the second listing associated with the entity is transmitted to the provider system. An indication that the second listing is suppressed on the provider system is received, where, in response to a request to access the second web address associated with the second listing, a web browser is redirected to the first web address associated with the first listing.

Abstract: A source system receives an indication to suppress a listing associated with an entity, wherein the indication is based at least in part on a confidence score from the source system indicating that the listing is a duplicate of a representative listing. A list of a provider systems that provide search results including the listing associated with the entity is identified. A first provider system is searched for a first listing matching the listing associated with the entity. The source system receives from the first provider system, a provider-supplied external identifier associated with the first listing. A request to suppress is transmitted to the first listing from a search result generated in response to a search request submitted via the first provider system.

Abstract: In one implementation, a method is provided that receives multiple potential listings associated with an entity. A listing is selected from the multiple listings and is designated as a representative listing of the entity. A first request is transmitted to synchronize the representative listing with the entity. Responsive to receiving an indication that a synchronization of the first listing and a web address corresponding with the entity is complete, transmitting to the provider system using an application programming interface, a second request to suppress a second listing of the plurality of potential listings as a duplicate listing. A communication is received from the provider system via the application programming interface that confirms that the second request to suppress the second listing from a search result generated by the provider system is accepted.

Abstract: A system and method to manage a data graph including data associated with a user system. The system and method receive multiple input document streams from multiple different data sources. A first document is identified from one of the multiple input document streams, the first document having a first schema including data associated with the user system. The first document is transformed from the first schema to a second schema to generate a first transformed document including at least a portion of the data. The portion of the data of the transformed first document is merged into the data graph stored in a graph database.

Abstract: A system and method to manage data associated with a merchant system to provide in response to a search query from an end user system. The system and method to generate, in a data graph associated with a merchant system, a first entity type including a first data field storing a first data value corresponding to the merchant system. A second entity type comprising a second data field storing a second data value corresponding to the merchant system is generated in the data graph. A relationship type between the first entity type and the second entity type is established. A first update to the first data value of the first entity type is generated. In view of the relationship type, a second update to the second data value of the second entity type is generated. The first update of the first entity type and the second update of the second entity type are stored in the data graph.

Abstract: A system and method to manage data associated with a merchant system to provide in response to a search query from an end user system. The system and method generate a custom entity type including one or more fields comprising first data corresponding to the merchant system. An update to the first data of the custom entity type can be received and an updated custom entity type is generated. The updated custom entity type is distributed to multiple business listing provider systems configured to provide search results associated with the merchant system in response to a search query from an end user system. The system and method can also generate a search experience interface including multiple input fields. The search experience interface is displayed to an end user to receive search terms via the first input and the second input field in response to a single search action.

Abstract: In one implementation, a method is provided that receives multiple potential listings associated with an entity. A listing is selected from the multiple listings and is designated as a representative listing of the entity. A first request is transmitted to synchronize the representative listing with the entity. Responsive to receiving an indication that a synchronization of the first listing and a web address corresponding with the entity is complete, transmitting to the provider system using an application programming interface, a second request to suppress a second listing of the plurality of potential listings as a duplicate listing. A communication is received from the provider system via the application programming interface that confirms that the second request to suppress the second listing from a search result generated by the provider system is accepted.

Abstract: In one implementation, a method is provided that receives multiple potential listings associated with an entity. A listing is selected from the multiple listings and is designated as a representative listing of the entity. A first request is transmitted to synchronize the representative listing with the entity. Responsive to an indication that a synchronization is complete, a second request is provided to suppress a second listing as a duplicate listing. A confirmation of the second request is received and the suppression of the second listing is verified.

Abstract: A source system receives an indication to suppress a listing associated with an entity, wherein the indication is based at least in part on a confidence score from the source system indicating that the listing is a duplicate of a representative listing. A list of a provider systems that provide search results including the listing associated with the entity is identified. A first provider system is searched for a first listing matching the listing associated with the entity. The source system receives from the first provider system, a provider-supplied external identifier associated with the first listing. A request to suppress is transmitted to the first listing from a search result generated in response to a search request submitted via the first provider system.

Abstract: A source system receives, from at least one of the user associated with an entity or the human operator associated with the source system, an indication to suppress all listings associated with the entity on one or more provider systems, wherein the indication comprises identification data of the entity and an indication that the identification data of the entity is no longer valid. The source system retrieves, from a database associated with the source system, a list of one or more provider systems associated with the source system and having at least one listing corresponding to the entity. For each provider system in the list of one or more provider systems: the source system searches the provider system for listings having identification data matching the identification data of the entity.

Abstract: In one implementation, a method is provided that receives multiple potential listings associated with an entity. A listing is selected from the multiple listings and is designated as a representative listing of the entity. A first request is transmitted to synchronize the representative listing with the entity. Responsive to an indication that a synchronization is complete, a second request is provided to suppress a second listing as a duplicate listing.

Abstract: In one implementation, a method is provided that comprises receiving a plurality of potential listings associated with an entity from a provider system. Each listing comprises a confidence score assigned by the provider system. A representative listing of the entity located on the provider system is designated from amongst the plurality of potential listings based on the confidence score. A first request is transmitted to synchronize the representative listing with the entity on the provider system. Responsive to receiving an indication that the request to synchronize is complete, a second request to suppress remaining listings of the potential listings as duplicates is provided. The remaining listings having confidence scores lower than the confidence score associated with the representative listing. The second request to suppress the remaining listings as duplicate listings is provided to the provider system using an API and a confirmation that the remaining listings are suppressed.

Abstract: In one implementation, a method is provided that comprises receiving a plurality of potential listings associated with an entity from a provider system. Each listing comprises a confidence score assigned by the provider system. A representative listing of the entity located on the provider system is designated from amongst the plurality of potential listings based on the confidence score. A first request is transmitted to synchronize the representative listing with the entity on the provider system. Responsive to receiving an indication that the request to synchronize is complete, a second request to suppress remaining listings of the potential listings as duplicates is provided. The remaining listings having confidence scores lower than the confidence score associated with the representative listing. The second request to suppress the remaining listings as duplicate listings is provided to the provider system using an API and a confirmation that the remaining listings are suppressed.

Abstract: A source system receives, from at least one of the user associated with an entity or the human operator associated with the source system, an indication to suppress all listings associated with the entity on one or more provider systems, wherein the indication comprises identification data of the entity and an indication that the identification data of the entity is no longer valid. The source system retrieves, from a database associated with the source system, a list of one or more provider systems associated with the source system and having at least one listing corresponding to the entity. For each provider system in the list of one or more provider systems: the source system searches the provider system for listings having identification data matching the identification data of the entity.

Abstract: A source system receives initial identification data of a listing related to an entity. The source system searches a provider system for one or more listings having identification data matching the initial identification data. The source system receives, from the provider system, a plurality of potential matching listings having identification data matching the initial identification data, wherein each listing of the plurality of potential matching listings has a corresponding confidence score assigned by the source system, and wherein each listing of the plurality of potential matching listings has a corresponding provider-supplied external identifier assigned by the provider system. The source system designates a representative listing of the entity located on a provider system from among the plurality of potential matching listings, the representative listing having the highest confidence score assigned by the source system.

Abstract: A server may receive from a mobile device, a first identifier identifying a service associated with a beacon device. The server may receive from the mobile device one or more identifiers associated with a physical location of the beacon device. The server may receive from the mobile device a device identifier associated with a user of the mobile device. The server may match the device identifier to an identifier in a list of device identifiers that correspond to a media slot controlled by an ad network of mobile devices that are in proximity to a location of a business in view of the first identifier and the one or more identifiers. The server may transmit to the mobile device an advertisement intended for mobile devices that are in proximity to the physical location associated with the beacon device.

Abstract: Responsive to selecting, by a source system, a representative listing of an entity located on a provider system, the representative listing having first identification data and a first provider-supplied external identifier, the source system searches the provider system for additional listings having identification data matching the first identification data. The source system receives, from the provider system, a potential matching listing having identification data matching the first identification data and having a second provider-supplied external identifier that differs from the first provider-supplied external identifier. The source system designates the potential matching listing as a duplicate listing. The source system transmits, to the provider system, a request to suppress the designated duplicate listing on the provider system, the request comprising the second provider-supplied external identifier.

Abstract: A server may receive, from a software development kit (SDK) installed in an application executed by a processor of a mobile device, a first identifier identifying a service associated with a beacon device. The server may receive from the SDK one or more identifiers associated with the physical location of the beacon device. The server may select an alert to transmit to the application of the mobile device comprising an in-application reward for performing an in-application service in view of the first identifier and the one or more identifiers. The server may transmit the alert to the application of the mobile device.