DoubleClick (DFP) FireDAC Components

Read, Write, & Update Google Ad Manager from Delphi and C++ Builder Apps

The fastest and easiest way to connect Delphi and C++ Builder Apps with live Google Ad Manager data.


  download   buy now

The Google Ad Manager FireDAC Component enables user to easily connect to Google Ad Manager data from Delphi & C++ Builder applications. An easy-to-use database-like interface for Delphi & C++Builder Apps to access live DoubleClick For Publishers data (Companies, Contacts, Placements, Users, and more).

Features

  • Connect to live Google Ad Manager data, for real-time data access
  • Full support for data aggregation and complex JOINs in SQL queries
  • Secure connectivity through modern cryptography, including TLS 1.2, SHA-256, ECC, etc.

Specifications

  • Native FireDAC Components for Google Ad Manager seamlessly integrate with RAD Studio
  • Comprehensive support for CRUD (Create, Read, Update, & Delete)
  • Full Unicode support for data, parameter, & metadata
  • Support for 32-bit & 64-bit operating systems
  • Requires Delphi, C++ Builder, or RAD Studio 10.2 Professional or higher

Windows
macOS
Unix

AVAILABLE IN:
FireDAC SUBSCRIPTIONS
150+ FireDAC Drivers For Real-Time Data Access
LEARN MORE

Where can I use the DoubleClick (DFP) FireDAC Components?

FireDAC Access to Google Ad Manager

Full-featured & consistent SQL access to any supported data source through FireDAC


  • Straightforward RAD Studio Integration

    Feature-rich high-performance Data Access Components that extend Delphi & C++ Builder Apps with SaaS, NoSQL, & Big Data connectivity.

  • Pure FireDAC Components

    Based on FireDAC Universal Data Access for developing applications for multiple devices, connected to enterprise databases.

  • Replication and Caching

    Our replication and caching commands make it easy to copy data to local and cloud data store as Oracle, SQL Server, Google Cloud SQL, etc. The replication commands include many features that allow for intelligent incremental updates to cached data.

  • String, Data, Numeric SQL Functions

    The driver includes a library of 50 plus functions that can manipulate column values into the desired result. Popular examples include Regex, JSON, and XML processing functions.

  • Developer Friendly

    Full Design-time support for data operations directly directly from RAD Studio. Work with live data directly from the IDE Data Explorer and FireDAC explorer.

  • Collaborative Query Processing

    Our drivers enhance the data source's capabilities by additional client side processing, when needed, to enable analytic summaries of data such as SUM, AVG, MAX, MIN, etc.

  • Easily Customizable & Configurable

    The data model exposed by our FireDAC Components can easily be customized to add or remove tables/columns, change data types, etc. without requiring a new build. These customizations are supported at runtime using human-readable schema files that are easy to edit.

  • Enterprise-class Secure Connectivity

    Includes standard Enterprise-class security features such as TLS/SSL data encryption for all client-server communications.

Standard FireDAC Access to Google Ad Manager

The DoubleClick (DFP) FireDAC Components offers the most natural way to access Google Ad Manager data from any Delphi or C++ Builder application. Simply use DoubleClick (DFP) FireDAC Components objects to connect and access data just as you would access any traditional database. You will be able to use the DoubleClick (DFP) FireDAC Components through RAD Studio, in code through familiar classes, and in data controls like TDBGrid, TDBCtrlGrid, etc.

The CData FireDAC Components for DoubleClick (DFP) hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.

Working with the FireDAC Components, etc.

The DoubleClick (DFP) FireDAC Components has the same architecture as the native Delphi & C++ Builder FireDAC Components for SQL Server and can be accessed the same way.

For example:

FDConnection1.Name := 'Google Ad ManagerConnection';
FDConnection1.DriverName := 'CData.Fire.Google Ad Manager';
with FDConnection1.Params as    
	TFDPhysCDataGoogle Ad ManagerConnectionDefParams do begin
	...
end;
FDConnection1.Connected := true;
FDQuery1.Active := true;
FDQuery1.Open('select * from Companies where id = ''...''');
...


More Than Read-Only: Full Update/CRUD Support

DoubleClick (DFP) FireDAC Components goes beyond read-only functionality to deliver full support for Create, Read, Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the DoubleClick (DFP) FireDAC Components as easily as interacting with a database table.


FireDAC Components Performance

With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:

  1. Network Connections - Slow network connections and latency issues are common in mobile applications.
  2. Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
  3. Large Data - Intentional or unintentional requests for large amounts of data.
  4. Disconnects - Complete loss of network connectivity.

The CData FireDAC Components for DoubleClick (DFP) solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.

Smart Caching

Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.

Caching with our FireDAC Componentss is highly configurable, including options for:

  • Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
  • Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
  • No Cache - All requests access only live data and no local cache file is created.

This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.

More information about FireDAC Components caching and best caching practices is available in the included help files.